Instruction And Logic For In-Order Handling In An Out-Of-Order Processor

ABSTRACT

In one embodiment, a processor includes a decode logic, an issue logic to issue decoded instructions, and at least one execution logic to execute issued instructions of a program. The at least one execution logic is to execute at least some instructions of the program out-of-order, and the decode logic is to decode and provide a first in-order memory instruction of the program to the issue logic. In turn, the issue logic is to order the first in-order memory instruction ahead of a second in-order memory instruction of the program. Other embodiments are described and claimed.

This application is a divisional of U.S. patent application Ser. No.14/953,644, filed Nov. 30, 2015, the content of which is herebyincorporated by reference.

FIELD OF THE INVENTION

The present disclosure pertains to the field of processing logic,microprocessors, and associated instruction set architecture that, whenexecuted by the processor or other processing logic, perform logical,mathematical, or other functional operations.

BACKGROUND

Out-of-order execution of instructions within a processor occurs forcertain compute intensive tasks like signal processing. However,in-order execution of memory mapped input/output (MMIO) accesses isrequired to guarantee correct execution in embedded controlapplications. To effect such operation, a programmer introduces special(e.g., fence/barrier) instructions to ensure in-order execution.However, this technique is error prone, and makes high-level code lessportable across instruction set architectures, less readable, and lessre-useable.

Historically, embedded systems such as small control units included inindustrial, automotive and other specialized environments werearchitected with an in-order processor architecture. As more computecomplex activities are performed in embedded applications, out-of-orderprocessing architectures are being introduced, which increasescomplexity and suffers from backwards compatibility issues with existingcode bases.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of an exemplary computer system formed with aprocessor that may include execution units to execute an instruction, inaccordance with embodiments of the present disclosure.

FIG. 1B illustrates a data processing system, in accordance withembodiments of the present disclosure.

FIG. 1C illustrates another embodiment of a data processing system toperform operations in accordance with embodiments of the presentdisclosure.

FIG. 2 is a block diagram of the micro-architecture for a processor thatmay include logic circuits to perform instructions, in accordance withembodiments of the present disclosure.

FIG. 3A illustrates various packed data type representations inmultimedia registers, in accordance with embodiments of the presentdisclosure.

FIG. 3B illustrates possible in-register data storage formats, inaccordance with embodiments of the present disclosure.

FIG. 3C illustrates various signed and unsigned packed data typerepresentations in multimedia registers, in accordance with embodimentsof the present disclosure.

FIG. 3D illustrates an embodiment of an operation encoding format.

FIG. 3E illustrates another possible operation encoding format havingforty or more bits, in accordance with embodiments of the presentdisclosure.

FIG. 3F illustrates yet another possible operation encoding format, inaccordance with embodiments of the present disclosure.

FIG. 4A is a block diagram illustrating an in-order pipeline and aregister renaming stage, out-of-order issue/execution pipeline, inaccordance with embodiments of the present disclosure.

FIG. 4B is a block diagram illustrating an in-order architecture coreand a register renaming logic, out-of-order issue/execution logic to beincluded in a processor, in accordance with embodiments of the presentdisclosure.

FIG. 5A is a block diagram of a processor, in accordance withembodiments of the present disclosure.

FIG. 5B is a block diagram of an example implementation of a core, inaccordance with embodiments of the present disclosure.

FIG. 6 is a block diagram of a system, in accordance with embodiments ofthe present disclosure.

FIG. 7 is a block diagram of a second system, in accordance withembodiments of the present disclosure.

FIG. 8 is a block diagram of a third system in accordance withembodiments of the present disclosure.

FIG. 9 is a block diagram of a system-on-a-chip, in accordance withembodiments of the present disclosure.

FIG. 10 illustrates a processor containing a central processing unit anda graphics processing unit which may perform at least one instruction,in accordance with embodiments of the present disclosure.

FIG. 11 is a block diagram illustrating the development of IP cores, inaccordance with embodiments of the present disclosure.

FIG. 12 illustrates how an instruction of a first type may be emulatedby a processor of a different type, in accordance with embodiments ofthe present disclosure.

FIG. 13 illustrates a block diagram contrasting the use of a softwareinstruction converter to convert binary instructions in a sourceinstruction set to binary instructions in a target instruction set, inaccordance with embodiments of the present disclosure.

FIG. 14 is a block diagram of an instruction set architecture of aprocessor, in accordance with embodiments of the present disclosure.

FIG. 15 is a more detailed block diagram of an instruction setarchitecture of a processor, in accordance with embodiments of thepresent disclosure.

FIG. 16 is a block diagram of an execution pipeline for an instructionset architecture of a processor, in accordance with embodiments of thepresent disclosure.

FIG. 17 is a block diagram of an electronic device for utilizing aprocessor, in accordance with embodiments of the present disclosure.

FIG. 18 is a flow diagram of a method in accordance with an embodimentof the present invention.

FIG. 19 is a flow diagram of a method in accordance with anotherembodiment of the present invention.

FIG. 20 is a flow diagram of a method for compiler execution inaccordance with an embodiment.

FIG. 21 is a flow diagram of a method for decoding instructions inaccordance with an embodiment of the present invention.

FIG. 22 is a flow diagram of a method in accordance with an embodimentof the present invention.

FIG. 23 is a block diagram of a portion of a processor in accordancewith an embodiment.

DETAILED DESCRIPTION

Embodiments provide an extended set of load and store instructions to beexecuted strictly in-order. Such instructions may be encoded intomachine language encodings that are different from out-of-ordercounterparts of such load/store instructions. In embodiments, aprocessor guarantees to execute and commit two such control instructionsonly in-order. Note that other instructions of the same program may beexecuted out-of-order.

To create such instructions in a program, a compiler may be configuredto identify appropriate load/store instructions amenable to in-orderexecution (as may be required for correct program operation). As oneexample, memory mapped input/output (MMIO) variables used in programssuch as device drivers can be identified with a compiler directive(e.g., a prefix in a variable declaration) that instructs the compilerto use in-order instructions for read/write access made to thosevariables. In embodiments, in-order load/store instructions, e.g.,control instructions, may be given a higher priority by a schedulingentity when selecting from a ready-to-execute queue of a processor.

Embodiments may provide more efficient operation and programming thaninstructions such as fence/barrier instructions inserted manually by aprogrammer. Operation using instructions as described herein also may bemore efficient than providing separate cores for control and computetasks, and/or a separate in-order mode.

Control-oriented code like a device driver involves many MMIOtransactions. MMIO transactions may execute in strict program order,since bitfields in two different registers might have to be written in acertain order to enable a particular hardware function. By providingin-order instructions as described herein, e.g., for MMIO transactions,load-load, store-store, or load-store dependency may only between theseMMIO transactions. By enabling compiler insertion of orderedinstructions in place of code written with out-of-order instructions,readability, robustness and portability of source code is realized.

Embodiments may be used in a variety of computing contexts including butnot limited to embedded systems. An interface can be used to specifyblocks of addresses that are to be accessed strictly in-order, to ensurecorrectness. As such, embodiments enable use of out-of-order processorsfor an embedded control domain.

Referring now to Table 1, shown is a sample high level declaration of aMMIO variable in accordance with an embodiment, in the C language.

TABLE 1 volatile mmio struct _sUart Uart _attribute_ ( (section(“UART_REG”) ) )

As illustrated in Table 1, this declaration provides a compiler prefix(referred to as MMIO) as a keyword to specify that this variable is aMMIO-mapped variable and thus is to be handled in-order as describedherein. In the particular example above, understand that the declarationis to define that all registers related to a particular device driver(here a universal asynchronous receiver/transmitter (UART)) mapped to agiven range of addresses are to be handled accordingly.

As an example, a text editor can be used to specify the keyword to thecompiler or a high-level code generation tool can be instructed to treata block of addresses as part of a peripheral device. As a result, thisin turn generates a code similar to a programmer-included code. Notethat this MMIO prefix is used here as an example; other terms can alsobe used based on keyword availability in compiler/applicationproperties.

Assume a code sequence is to write information to given registers, e.g.,transceiver registers (uart.data and uart.trigger registers), and thenpoll on the uart.status register. High level source code of suchoperation is illustrated in Table 2.

TABLE 2 #define UART_TX_TRIGGER (1 << 4) #define UART_TX_COMPLETE 1 voiduart_send_data (char data) {    int c;    Uart.data = (unsigned int)data;  /*Write the data to be    transmitted */    Uart.trigger =Uart.trigger | UART_TX_TRIGGER;    while (Uart.status !=UART_TX_COMPLETE);    return; }

As seen, this source code is to write data to be transmitted into a dataregister (Uart_data), perform a logical operation with a triggerregister and transmit the data until the trigger condition is met. Morespecifically, the code enables a write to the Uart.data register withthe data to be transmitted, followed by instructing the Uart to startthe transmit by writing to the Uart.trigger register. Then the flowwaits until the Uart finishes sending the data via a one-line Whileloop. Note that the hardware will set Uart status==ART_TX_COMPLETE onlyafter the transmit operation is complete. Note that the variousvariables associated with the Uart definition (Uart.data, Uart.trigger,and Uart.status) are thus associated with the compiler directive and assuch, a compiler is to generate in-order load/store instructions forinstructions referencing these source code variables as operands. Thissource code, when compiled on a given machine, may be translated intomachine code, e.g., into assembly language.

Table 3 below shows translated code without providing in-orderinstructions as described herein.

TABLE 3 movsx eax, BYTE PTR [esp+0x4] mov ds:0x0,eax → ds:0x0 −>Uart.data register mov eax,ds : 0x4 or eax, 0x10 mov ds : 0x4, eax →dx:0x4 −> Uart.trigger register mov eax, ds : 0x8 → ds:0x8 −>Uart.status register cmp eax, 0x1 jne 17 <_uart_send_data+0x17> ret nopnop

An out-of-order processor can see independent threads of execution inthis code, as there are no data dependencies between them. And thusthere are no data hazards from the processor point of view. But inreality, the code is not independent due to sequencing requirementimposed by Uart hardware.

Embodiments provide instruction set architecture instructions to performin-order load/store operations. Example instruction encoding includes aso-called emov instruction. In one embodiment, this instruction may be auser-level instruction to be used by a programmer to specify in-orderexecution of a load/store instruction. In other embodiments, theinstruction may be a compiler-generated instruction (such as a machinecode instruction), generated responsive to an unordered user levelload/store instruction of source code. More generally, theseinstructions may be referred to as control instructions to denote thein-order control of such instructions. The implementation can be donewith microcode in a microcode-based system, or with dedicated hardwarein processors with hardware decoding.

Embodiments thus provide an out-of-order processor having an instructionset, out of which a group of instructions has an ISA level guarantee toexecute and commit in order. Note that a source version of a program mayprovide the instructions in order. In a conventional out-of-orderprocessor, an instruction decoder (and issue logic) may disregard thisordering. But using a processor in accordance with an embodiment, thedecoder (and the issue logic) will not disregard this information forthe in-order instructions described herein.

In one example, a control move instruction in accordance with anembodiment has the mnemonic, emove. An example of instruction encodingfor this instruction is: emov EAX, [address]. With this encoding, theinstruction may cause a move operation to move information at theidentified address to the EAX register. Note that this instruction maybe ordered with respect to a previous emov instruction, and certainprevious load/stores (e.g., an unordered moves). That is, a controlinstruction in accordance with an embodiment of the present inventionwill inherit all the ordering rules of its standard counterpart. Inaddition, it will impose ordering with respect to a previous controlinstruction. In this case an emov instruction inherits all orderingrules of a mov instruction. In addition, it is strictly ordered withrespect to previous control instructions. For example, assume a mov AX,0xa5a5 followed by emov [0xE5010000], AX. In a processor in accordancewith an embodiment of the present invention, these two instructions maybe ordered because the AX register is a common resource. This is anordering rule inherited from a mov instruction.

Referring now to Table 4, shown is a generated assembly code inaccordance with an embodiment that provides for in-order instructions.Now previously independent threads of execution are no longerindependent from the processor view point, because the emov instructionensures in-order execution among other emov instructions.

TABLE 4 movsx eax, BYTE PTR [esp+0x4] emov ds:0x0,eax → ds:0x0 −>Uart.data register emov eax,ds : 0x4 or eax, 0x10 emov ds : 0x4, eax →dx:0x4 −> Uart.trigger register emov eax, ds : 0x8 → ds:0x8 −>Uart.status register cmp eax, 0x1 jne 17 <_uart_send_data+0x17> ret nopnop

Although the following embodiments are described with reference to aprocessor, other embodiments are applicable to other types of integratedcircuits and logic devices. Similar techniques and teachings ofembodiments of the present disclosure may be applied to other types ofcircuits or semiconductor devices that may benefit from higher pipelinethroughput and improved performance. The teachings of embodiments of thepresent disclosure are applicable to any processor or machine thatperforms data manipulations. However, the embodiments are not limited toprocessors or machines that perform 512-bit, 256-bit, 128-bit, 64-bit,32-bit, or 16-bit data operations and may be applied to any processorand machine in which manipulation or management of data may beperformed. In addition, the following description provides examples, andthe accompanying drawings show various examples for the purposes ofillustration. However, these examples should not be construed in alimiting sense as they are merely intended to provide examples ofembodiments of the present disclosure rather than to provide anexhaustive list of all possible implementations of embodiments of thepresent disclosure.

Although the below examples describe instruction handling anddistribution in the context of execution units and logic circuits, otherembodiments of the present disclosure may be accomplished by way of adata or instructions stored on a machine-readable, tangible medium,which when performed by a machine cause the machine to perform functionsconsistent with at least one embodiment of the disclosure. In oneembodiment, functions associated with embodiments of the presentdisclosure are embodied in machine-executable instructions. Theinstructions may be used to cause a general-purpose or special-purposeprocessor that may be programmed with the instructions to perform thesteps of the present disclosure. Embodiments of the present disclosuremay be provided as a computer program product or software which mayinclude a machine or computer-readable medium having stored thereoninstructions which may be used to program a computer (or otherelectronic devices) to perform one or more operations according toembodiments of the present disclosure. Furthermore, steps of embodimentsof the present disclosure might be performed by specific hardwarecomponents that contain fixed-function logic for performing the steps,or by any combination of programmed computer components andfixed-function hardware components.

Instructions used to program logic to perform embodiments of the presentdisclosure may be stored within a memory in the system, such as DRAM,cache, flash memory, or other storage. Furthermore, the instructions maybe distributed via a network or by way of other computer-readable media.Thus a machine-readable medium may include any mechanism for storing ortransmitting information in a form readable by a machine (e.g., acomputer), but is not limited to, floppy diskettes, optical disks,Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks,Read-Only Memory (ROMs), Random Access Memory (RAM), ErasableProgrammable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), magnetic or optical cards, flashmemory, or a tangible, machine-readable storage used in the transmissionof information over the Internet via electrical, optical, acoustical orother forms of propagated signals (e.g., carrier waves, infraredsignals, digital signals, etc.). Accordingly, the computer-readablemedium may include any type of tangible machine-readable medium suitablefor storing or transmitting electronic instructions or information in aform readable by a machine (e.g., a computer).

A design may go through various stages, from creation to simulation tofabrication. Data representing a design may represent the design in anumber of manners. First, as may be useful in simulations, the hardwaremay be represented using a hardware description language or anotherfunctional description language. Additionally, a circuit level modelwith logic and/or transistor gates may be produced at some stages of thedesign process. Furthermore, designs, at some stage, may reach a levelof data representing the physical placement of various devices in thehardware model. In cases wherein some semiconductor fabricationtechniques are used, the data representing the hardware model may be thedata specifying the presence or absence of various features on differentmask layers for masks used to produce the integrated circuit. In anyrepresentation of the design, the data may be stored in any form of amachine-readable medium. A memory or a magnetic or optical storage suchas a disc may be the machine-readable medium to store informationtransmitted via optical or electrical wave modulated or otherwisegenerated to transmit such information. When an electrical carrier waveindicating or carrying the code or design is transmitted, to the extentthat copying, buffering, or retransmission of the electrical signal isperformed, a new copy may be made. Thus, a communication provider or anetwork provider may store on a tangible, machine-readable medium, atleast temporarily, an article, such as information encoded into acarrier wave, embodying techniques of embodiments of the presentdisclosure.

In modern processors, a number of different execution units may be usedto process and execute a variety of code and instructions. Someinstructions may be quicker to complete while others may take a numberof clock cycles to complete. The faster the throughput of instructions,the better the overall performance of the processor. Thus it would beadvantageous to have as many instructions execute as fast as possible.However, there may be certain instructions that have greater complexityand require more in terms of execution time and processor resources,such as floating point instructions, load/store operations, data moves,etc.

As more computer systems are used in internet, text, and multimediaapplications, additional processor support has been introduced overtime. In one embodiment, an instruction set may be associated with oneor more computer architectures, including data types, instructions,register architecture, addressing modes, memory architecture, interruptand exception handling, and external input and output (I/O).

In one embodiment, the instruction set architecture (ISA) may beimplemented by one or more micro-architectures, which may includeprocessor logic and circuits used to implement one or more instructionsets. Accordingly, processors with different micro-architectures mayshare at least a portion of a common instruction set. For example,Intel® Pentium 4 processors, Intel® Core™ processors, and processorsfrom Advanced Micro Devices, Inc. of Sunnyvale Calif. implement nearlyidentical versions of the x86 instruction set (with some extensions thathave been added with newer versions), but have different internaldesigns. Similarly, processors designed by other processor developmentcompanies, such as ARM Holdings, Ltd., MIPS, or their licensees oradopters, may share at least a portion a common instruction set, but mayinclude different processor designs. For example, the same registerarchitecture of the ISA may be implemented in different ways indifferent micro-architectures using new or well-known techniques,including dedicated physical registers, one or more dynamicallyallocated physical registers using a register renaming mechanism (e.g.,the use of a Register Alias Table (RAT), a Reorder Buffer (ROB) and aretirement register file. In one embodiment, registers may include oneor more registers, register architectures, register files, or otherregister sets that may or may not be addressable by a softwareprogrammer.

An instruction may include one or more instruction formats. In oneembodiment, an instruction format may indicate various fields (number ofbits, location of bits, etc.) to specify, among other things, theoperation to be performed and the operands on which that operation willbe performed. In a further embodiment, some instruction formats may befurther defined by instruction templates (or sub-formats). For example,the instruction templates of a given instruction format may be definedto have different subsets of the instruction format's fields and/ordefined to have a given field interpreted differently. In oneembodiment, an instruction may be expressed using an instruction format(and, if defined, in a given one of the instruction templates of thatinstruction format) and specifies or indicates the operation and theoperands upon which the operation will operate.

Scientific, financial, auto-vectorized general purpose, RMS(recognition, mining, and synthesis), and visual and multimediaapplications (e.g., 2D/3D graphics, image processing, videocompression/decompression, voice recognition algorithms and audiomanipulation) may require the same operation to be performed on a largenumber of data items. In one embodiment, Single Instruction MultipleData (SIMD) refers to a type of instruction that causes a processor toperform an operation on multiple data elements. SIMD technology may beused in processors that may logically divide the bits in a register intoa number of fixed-sized or variable-sized data elements, each of whichrepresents a separate value. For example, in one embodiment, the bits ina 64-bit register may be organized as a source operand containing fourseparate 16-bit data elements, each of which represents a separate16-bit value. This type of data may be referred to as ‘packed’ data typeor ‘vector’ data type, and operands of this data type may be referred toas packed data operands or vector operands. In one embodiment, a packeddata item or vector may be a sequence of packed data elements storedwithin a single register, and a packed data operand or a vector operandmay a source or destination operand of a SIMD instruction (or ‘packeddata instruction’ or a ‘vector instruction’). In one embodiment, a SIMDinstruction specifies a single vector operation to be performed on twosource vector operands to generate a destination vector operand (alsoreferred to as a result vector operand) of the same or different size,with the same or different number of data elements, and in the same ordifferent data element order.

SIMD technology, such as that employed by the Intel® Core™ processorshaving an instruction set including x86, MMX™, Streaming SIMD Extensions(SSE), SSE2, SSE3, SSE4.1, and SSE4.2 instructions, ARM processors, suchas the ARM Cortex® family of processors having an instruction setincluding the Vector Floating Point (VFP) and/or NEON instructions, andMIPS processors, such as the Loongson family of processors developed bythe Institute of Computing Technology (ICT) of the Chinese Academy ofSciences, has enabled a significant improvement in applicationperformance (Core™ and MMX™ are registered trademarks or trademarks ofIntel Corporation of Santa Clara, Calif).

In one embodiment, destination and source registers/data may be genericterms to represent the source and destination of the corresponding dataor operation. In some embodiments, they may be implemented by registers,memory, or other storage areas having other names or functions thanthose depicted. For example, in one embodiment, “DEST1” may be atemporary storage register or other storage area, whereas “SRC1” and“SRC2” may be a first and second source storage register or otherstorage area, and so forth. In other embodiments, two or more of the SRCand DEST storage areas may correspond to different data storage elementswithin the same storage area (e.g., a SIMD register). In one embodiment,one of the source registers may also act as a destination register by,for example, writing back the result of an operation performed on thefirst and second source data to one of the two source registers servingas a destination registers.

FIG. 1A is a block diagram of an exemplary computer system formed with aprocessor that may include execution units to execute an instruction, inaccordance with embodiments of the present disclosure. System 100 mayinclude a component, such as a processor 102 to employ execution unitsincluding logic to perform algorithms for process data, in accordancewith the present disclosure, such as in the embodiment described herein.System 100 may be representative of processing systems based on thePENTIUM™ III, PENTIUM™ 4, Xeon™, Itanium™, XScale™ and/or StrongARM™microprocessors available from Intel Corporation of Santa Clara, Calif.,although other systems (including PCs having other microprocessors,engineering workstations, set-top boxes and the like) may also be used.In one embodiment, sample system 100 may execute a version of theWINDOWS™ operating system available from Microsoft Corporation ofRedmond, Wash., although other operating systems (UNIX and Linux forexample), embedded software, and/or graphical user interfaces, may alsobe used. Thus, embodiments of the present disclosure are not limited toany specific combination of hardware circuitry and software.

Embodiments are not limited to computer systems. Embodiments of thepresent disclosure may be used in other devices such as handheld devicesand embedded applications. Some examples of handheld devices includecellular phones, Internet Protocol devices, digital cameras, personaldigital assistants (PDAs), and handheld PCs. Embedded applications mayinclude a micro controller, a digital signal processor (DSP), system ona chip, network computers (NetPC), set-top boxes, network hubs, widearea network (WAN) switches, or any other system that may perform one ormore instructions in accordance with at least one embodiment.

Computer system 100 may include a processor 102 that may include one ormore execution units 108 to perform an algorithm to perform at least oneinstruction in accordance with one embodiment of the present disclosure.One embodiment may be described in the context of a single processordesktop or server system, but other embodiments may be included in amultiprocessor system. System 100 may be an example of a ‘hub’ systemarchitecture. System 100 may include a processor 102 for processing datasignals. Processor 102 may include a complex instruction set computer(CISC) microprocessor, a reduced instruction set computing (RISC)microprocessor, a very long instruction word (VLIW) microprocessor, aprocessor implementing a combination of instruction sets, or any otherprocessor device, such as a digital signal processor, for example. Inone embodiment, processor 102 may be coupled to a processor bus 110 thatmay transmit data signals between processor 102 and other components insystem 100. The elements of system 100 may perform conventionalfunctions that are well known to those familiar with the art.

In one embodiment, processor 102 may include a Level 1 (L1) internalcache memory 104. Depending on the architecture, the processor 102 mayhave a single internal cache or multiple levels of internal cache. Inanother embodiment, the cache memory may reside external to processor102. Other embodiments may also include a combination of both internaland external caches depending on the particular implementation andneeds. Register file 106 may store different types of data in variousregisters including integer registers, floating point registers, statusregisters, and instruction pointer register.

Execution unit 108, including logic to perform integer and floatingpoint operations, also resides in processor 102. Processor 102 may alsoinclude a microcode (ucode) ROM that stores microcode for certainmacroinstructions. In one embodiment, execution unit 108 may includelogic to handle a packed instruction set 109. By including the packedinstruction set 109 in the instruction set of a general-purposeprocessor 102, along with associated circuitry to execute theinstructions, the operations used by many multimedia applications may beperformed using packed data in a general-purpose processor 102. Thus,many multimedia applications may be accelerated and executed moreefficiently by using the full width of a processor's data bus forperforming operations on packed data. This may eliminate the need totransfer smaller units of data across the processor's data bus toperform one or more operations one data element at a time.

Embodiments of an execution unit 108 may also be used in microcontrollers, embedded processors, graphics devices, DSPs, and othertypes of logic circuits. System 100 may include a memory 120. Memory 120may be implemented as a dynamic random access memory (DRAM) device, astatic random access memory (SRAM) device, flash memory device, or othermemory device. Memory 120 may store instructions and/or data representedby data signals that may be executed by processor 102.

A system logic chip 116 may be coupled to processor bus 110 and memory120. System logic chip 116 may include a memory controller hub (MCH).Processor 102 may communicate with MCH 116 via a processor bus 110. MCH116 may provide a high bandwidth memory path 118 to memory 120 forinstruction and data storage and for storage of graphics commands, dataand textures. MCH 116 may direct data signals between processor 102,memory 120, and other components in system 100 and to bridge the datasignals between processor bus 110, memory 120, and system I/O 122. Insome embodiments, the system logic chip 116 may provide a graphics portfor coupling to a graphics controller 112. MCH 116 may be coupled tomemory 120 through a memory interface 118. Graphics card 112 may becoupled to MCH 116 through an Accelerated Graphics Port (AGP)interconnect 114.

System 100 may use a proprietary hub interface bus 122 to couple MCH 116to I/O controller hub (ICH) 130. In one embodiment, ICH 130 may providedirect connections to some I/O devices via a local I/O bus. The localI/O bus may include a high-speed I/O bus for connecting peripherals tomemory 120, chipset, and processor 102. Examples may include the audiocontroller, firmware hub (flash BIOS) 128, wireless transceiver 126,data storage 124, legacy I/O controller containing user input andkeyboard interfaces, a serial expansion port such as Universal SerialBus (USB), and a network controller 134. Data storage device 124 maycomprise a hard disk drive, a floppy disk drive, a CD-ROM device, aflash memory device, or other mass storage device.

For another embodiment of a system, an instruction in accordance withone embodiment may be used with a system on a chip. One embodiment of asystem on a chip comprises of a processor and a memory. The memory forone such system may include a flash memory. The flash memory may belocated on the same die as the processor and other system components.Additionally, other logic blocks such as a memory controller or graphicscontroller may also be located on a system on a chip.

FIG. 1B illustrates a data processing system 140 which implements theprinciples of embodiments of the present disclosure. It will be readilyappreciated by one of skill in the art that the embodiments describedherein may operate with alternative processing systems without departurefrom the scope of embodiments of the disclosure.

Computer system 140 comprises a processing core 159 for performing atleast one instruction in accordance with one embodiment. In oneembodiment, processing core 159 represents a processing unit of any typeof architecture, including but not limited to a CISC, a RISC or a VLIWtype architecture. Processing core 159 may also be suitable formanufacture in one or more process technologies and by being representedon a machine-readable media in sufficient detail, may be suitable tofacilitate said manufacture.

Processing core 159 comprises an execution unit 142, a set of registerfiles 145, and a decoder 144. Processing core 159 may also includeadditional circuitry (not shown) which may be unnecessary to theunderstanding of embodiments of the present disclosure. Execution unit142 may execute instructions received by processing core 159. Inaddition to performing typical processor instructions, execution unit142 may perform instructions in packed instruction set 143 forperforming operations on packed data formats. Packed instruction set 143may include instructions for performing embodiments of the disclosureand other packed instructions. Execution unit 142 may be coupled toregister file 145 by an internal bus. Register file 145 may represent astorage area on processing core 159 for storing information, includingdata. As previously mentioned, it is understood that the storage areamay store the packed data might not be critical. Execution unit 142 maybe coupled to decoder 144. Decoder 144 may decode instructions receivedby processing core 159 into control signals and/or microcode entrypoints. In response to these control signals and/or microcode entrypoints, execution unit 142 performs the appropriate operations. In oneembodiment, the decoder may interpret the opcode of the instruction,which will indicate what operation should be performed on thecorresponding data indicated within the instruction.

Processing core 159 may be coupled with bus 141 for communicating withvarious other system devices, which may include but are not limited to,for example, synchronous dynamic random access memory (SDRAM) control146, static random access memory (SRAM) control 147, burst flash memoryinterface 148, personal computer memory card international association(PCMCIA)/compact flash (CF) card control 149, liquid crystal display(LCD) control 150, direct memory access (DMA) controller 151, andalternative bus master interface 152. In one embodiment, data processingsystem 140 may also comprise an I/O bridge 154 for communicating withvarious I/O devices via an I/O bus 153. Such I/O devices may include butare not limited to, for example, universal asynchronousreceiver/transmitter (UART) 155, universal serial bus (USB) 156,Bluetooth wireless UART 157 and I/O expansion interface 158.

One embodiment of data processing system 140 provides for mobile,network and/or wireless communications and a processing core 159 thatmay perform SIMD operations including a text string comparisonoperation. Processing core 159 may be programmed with various audio,video, imaging and communications algorithms including discretetransformations such as a Walsh-Hadamard transform, a fast Fouriertransform (FFT), a discrete cosine transform (DCT), and their respectiveinverse transforms; compression/decompression techniques such as colorspace transformation, video encode motion estimation or video decodemotion compensation; and modulation/demodulation (MODEM) functions suchas pulse coded modulation (PCM).

FIG. 1C illustrates another embodiment of a data processing system toperform operations in accordance with embodiments of the presentdisclosure. In one embodiment, data processing system 160 may include amain processor 166, a SIMD coprocessor 161, a cache memory 167, and aninput/output system 168. Input/output system 168 may optionally becoupled to a wireless interface 169. SIMD coprocessor 161 may performoperations including instructions in accordance with one embodiment. Inone embodiment, processing core 170 may be suitable for manufacture inone or more process technologies and by being represented on amachine-readable media in sufficient detail, may be suitable tofacilitate the manufacture of all or part of data processing system 160including processing core 170.

In one embodiment, SIMD coprocessor 161 comprises an execution unit 162and a set of register files 164. One embodiment of main processor 165comprises a decoder 165 to recognize instructions of instruction set 163including instructions in accordance with one embodiment for executionby execution unit 162. In other embodiments, SIMD coprocessor 161 alsocomprises at least part of decoder 165 to decode instructions ofinstruction set 163. Processing core 170 may also include additionalcircuitry (not shown) which may be unnecessary to the understanding ofembodiments of the present disclosure.

In operation, main processor 166 executes a stream of data processinginstructions that control data processing operations of a general typeincluding interactions with cache memory 167, and input/output system168. Embedded within the stream of data processing instructions may beSIMD coprocessor instructions. Decoder 165 of main processor 166recognizes these SIMD coprocessor instructions as being of a type thatshould be executed by an attached SIMD coprocessor 161. Accordingly,main processor 166 issues these SIMD coprocessor instructions (orcontrol signals representing SIMD coprocessor instructions) on thecoprocessor bus 166. From coprocessor bus 166, these instructions may bereceived by any attached SIMD coprocessors. In this case, SIMDcoprocessor 161 may accept and execute any received SIMD coprocessorinstructions intended for it.

Data may be received via wireless interface 169 for processing by theSIMD coprocessor instructions. For one example, voice communication maybe received in the form of a digital signal, which may be processed bythe SIMD coprocessor instructions to regenerate digital audio samplesrepresentative of the voice communications. For another example,compressed audio and/or video may be received in the form of a digitalbit stream, which may be processed by the SIMD coprocessor instructionsto regenerate digital audio samples and/or motion video frames. In oneembodiment of processing core 170, main processor 166, and a SIMDcoprocessor 161 may be integrated into a single processing core 170comprising an execution unit 162, a set of register files 164, and adecoder 165 to recognize instructions of instruction set 163 includinginstructions in accordance with one embodiment.

FIG. 2 is a block diagram of the micro-architecture for a processor 200that may include logic circuits to perform instructions, in accordancewith embodiments of the present disclosure. In some embodiments, aninstruction in accordance with one embodiment may be implemented tooperate on data elements having sizes of byte, word, doubleword,quadword, etc., as well as datatypes, such as single and doubleprecision integer and floating point datatypes. In one embodiment,in-order front end 201 may implement a part of processor 200 that mayfetch instructions to be executed and prepares the instructions to beused later in the processor pipeline. Front end 201 may include severalunits. In one embodiment, instruction prefetcher 226 fetchesinstructions from memory and feeds the instructions to an instructiondecoder 228 which in turn decodes or interprets the instructions. Forexample, in one embodiment, the decoder decodes a received instructioninto one or more operations called “micro-instructions” or“micro-operations” (also called micro op or uops) that the machine mayexecute. In other embodiments, the decoder parses the instruction intoan opcode and corresponding data and control fields that may be used bythe micro-architecture to perform operations in accordance with oneembodiment. In one embodiment, trace cache 230 may assemble decoded uopsinto program ordered sequences or traces in uop queue 234 for execution.When trace cache 230 encounters a complex instruction, microcode ROM 232provides the uops needed to complete the operation.

Some instructions may be converted into a single micro-op, whereasothers need several micro-ops to complete the full operation. In oneembodiment, if more than four micro-ops are needed to complete aninstruction, decoder 228 may access microcode ROM 232 to perform theinstruction. In one embodiment, an instruction may be decoded into asmall number of micro ops for processing at instruction decoder 228. Inanother embodiment, an instruction may be stored within microcode ROM232 should a number of micro-ops be needed to accomplish the operation.Trace cache 230 refers to an entry point programmable logic array (PLA)to determine a correct micro-instruction pointer for reading themicro-code sequences to complete one or more instructions in accordancewith one embodiment from micro-code ROM 232. After microcode ROM 232finishes sequencing micro-ops for an instruction, front end 201 of themachine may resume fetching micro-ops from trace cache 230.

Out-of-order execution engine 203 may prepare instructions forexecution. The out-of-order execution logic has a number of buffers tosmooth out and re-order the flow of instructions to optimize performanceas they go down the pipeline and get scheduled for execution. Theallocator logic allocates the machine buffers and resources that eachuop needs in order to execute. The register renaming logic renames logicregisters onto entries in a register file. The allocator also allocatesan entry for each uop in one of the two uop queues, one for memoryoperations and one for non-memory operations, in front of theinstruction schedulers: memory scheduler, fast scheduler 202,slow/general floating point scheduler 204, and simple floating pointscheduler 206. Uop schedulers 202, 204, 206, determine when a uop isready to execute based on the readiness of their dependent inputregister operand sources and the availability of the execution resourcesthe uops need to complete their operation. Fast scheduler 202 of oneembodiment may schedule on each half of the main clock cycle while theother schedulers may only schedule once per main processor clock cycle.The schedulers arbitrate for the dispatch ports to schedule uops forexecution.

Register files 208, 210 may be arranged between schedulers 202, 204,206, and execution units 212, 214, 216, 218, 220, 222, 224 in executionblock 211. Each of register files 208, 210 perform integer and floatingpoint operations, respectively. Each register file 208, 210, may includea bypass network that may bypass or forward just completed results thathave not yet been written into the register file to new dependent uops.Integer register file 208 and floating point register file 210 maycommunicate data with the other. In one embodiment, integer registerfile 208 may be split into two separate register files, one registerfile for low-order thirty-two bits of data and a second register filefor high order thirty-two bits of data. Floating point register file 210may include 128-bit wide entries because floating point instructionstypically have operands from 64 to 128 bits in width.

Execution block 211 may contain execution units 212, 214, 216, 218, 220,222, 224. Execution units 212, 214, 216, 218, 220, 222, 224 may executethe instructions. Execution block 211 may include register files 208,210 that store the integer and floating point data operand values thatthe micro-instructions need to execute. In one embodiment, processor 200may comprise a number of execution units: address generation unit (AGU)212, AGU 214, fast ALU 216, fast ALU 218, slow ALU 220, floating pointALU 222, floating point move unit 224. In another embodiment, floatingpoint execution blocks 222, 224, may execute floating point, MMX, SIMD,and SSE, or other operations. In yet another embodiment, floating pointALU 222 may include a 64-bit by 64-bit floating point divider to executedivide, square root, and remainder micro-ops. In various embodiments,instructions involving a floating point value may be handled with thefloating point hardware. In one embodiment, ALU operations may be passedto high-speed ALU execution units 216, 218. High-speed ALUs 216, 218 mayexecute fast operations with an effective latency of half a clock cycle.In one embodiment, most complex integer operations go to slow ALU 220 asslow ALU 220 may include integer execution hardware for long-latencytype of operations, such as a multiplier, shifts, flag logic, and branchprocessing. Memory load/store operations may be executed by AGUs 212,214. In one embodiment, integer ALUs 216, 218, 220 may perform integeroperations on 64-bit data operands. In other embodiments, ALUs 216, 218,220 may be implemented to support a variety of data bit sizes includingsixteen, thirty-two, 128, 256, etc. Similarly, floating point units 222,224 may be implemented to support a range of operands having bits ofvarious widths. In one embodiment, floating point units 222, 224, mayoperate on 128-bit wide packed data operands in conjunction with SIMDand multimedia instructions.

In one embodiment, uops schedulers 202, 204, 206, dispatch dependentoperations before the parent load has finished executing. As uops may bespeculatively scheduled and executed in processor 200, processor 200 mayalso include logic to handle memory misses. If a data load misses in thedata cache, there may be dependent operations in flight in the pipelinethat have left the scheduler with temporarily incorrect data. A replaymechanism tracks and re-executes instructions that use incorrect data.Only the dependent operations might need to be replayed and theindependent ones may be allowed to complete. The schedulers and replaymechanism of one embodiment of a processor may also be designed to catchinstruction sequences for text string comparison operations.

The term “registers” may refer to the on-board processor storagelocations that may be used as part of instructions to identify operands.In other words, registers may be those that may be usable from theoutside of the processor (from a programmer's perspective). However, insome embodiments registers might not be limited to a particular type ofcircuit. Rather, a register may store data, provide data, and performthe functions described herein. The registers described herein may beimplemented by circuitry within a processor using any number ofdifferent techniques, such as dedicated physical registers, dynamicallyallocated physical registers using register renaming, combinations ofdedicated and dynamically allocated physical registers, etc. In oneembodiment, integer registers store 32-bit integer data. A register fileof one embodiment also contains eight multimedia SIMD registers forpacked data. For the discussions below, the registers may be understoodto be data registers designed to hold packed data, such as 64-bit wideMMX™ registers (also referred to as ‘mm’ registers in some instances) inmicroprocessors enabled with MMX technology from Intel Corporation ofSanta Clara, Calif. These MMX registers, available in both integer andfloating point forms, may operate with packed data elements thataccompany SIMD and SSE instructions. Similarly, 128-bit wide XMMregisters relating to SSE2, SSE3, SSE4, or beyond (referred togenerically as “SSEx”) technology may hold such packed data operands. Inone embodiment, in storing packed data and integer data, the registersdo not need to differentiate between the two data types. In oneembodiment, integer and floating point may be contained in the sameregister file or different register files. Furthermore, in oneembodiment, floating point and integer data may be stored in differentregisters or the same registers.

In the examples of the following figures, a number of data operands maybe described. FIG. 3A illustrates various packed data typerepresentations in multimedia registers, in accordance with embodimentsof the present disclosure. FIG. 3A illustrates data types for a packedbyte 310, a packed word 320, and a packed doubleword (dword) 330 for128-bit wide operands. Packed byte format 310 of this example may be 128bits long and contains sixteen packed byte data elements. A byte may bedefined, for example, as eight bits of data. Information for each bytedata element may be stored in bit 7 through bit 0 for byte 0, bit 15through bit 8 for byte 1, bit 23 through bit 16 for byte 2, and finallybit 120 through bit 127 for byte 15. Thus, all available bits may beused in the register. This storage arrangement increases the storageefficiency of the processor. As well, with sixteen data elementsaccessed, one operation may now be performed on sixteen data elements inparallel.

Generally, a data element may include an individual piece of data thatis stored in a single register or memory location with other dataelements of the same length. In packed data sequences relating to SSExtechnology, the number of data elements stored in a XMM register may be128 bits divided by the length in bits of an individual data element.Similarly, in packed data sequences relating to MMX and SSE technology,the number of data elements stored in an MMX register may be 64 bitsdivided by the length in bits of an individual data element. Althoughthe data types illustrated in FIG. 3A may be 128 bits long, embodimentsof the present disclosure may also operate with 64-bit wide or othersized operands. Packed word format 320 of this example may be 128 bitslong and contains eight packed word data elements. Each packed wordcontains sixteen bits of information. Packed doubleword format 330 ofFIG. 3A may be 128 bits long and contains four packed doubleword dataelements. Each packed doubleword data element contains thirty-two bitsof information. A packed quadword may be 128 bits long and contain twopacked quad-word data elements.

FIG. 3B illustrates possible in-register data storage formats, inaccordance with embodiments of the present disclosure. Each packed datamay include more than one independent data element. Three packed dataformats are illustrated; packed half 341, packed single 342, and packeddouble 343. One embodiment of packed half 341, packed single 342, andpacked double 343 contain fixed-point data elements. For anotherembodiment one or more of packed half 341, packed single 342, and packeddouble 343 may contain floating-point data elements. One embodiment ofpacked half 341 may be 128 bits long containing eight 16-bit dataelements. One embodiment of packed single 342 may be 128 bits long andcontains four 32-bit data elements. One embodiment of packed double 343may be 128 bits long and contains two 64-bit data elements. It will beappreciated that such packed data formats may be further extended toother register lengths, for example, to 96-bits, 160-bits, 192-bits,224-bits, 256-bits or more.

FIG. 3C illustrates various signed and unsigned packed data typerepresentations in multimedia registers, in accordance with embodimentsof the present disclosure. Unsigned packed byte representation 344illustrates the storage of an unsigned packed byte in a SIMD register.Information for each byte data element may be stored in bit 7 throughbit 0 for byte 0, bit 15 through bit 8 for byte 1, bit 23 through bit 16for byte 2, and finally bit 120 through bit 127 for byte 15. Thus, allavailable bits may be used in the register. This storage arrangement mayincrease the storage efficiency of the processor. As well, with sixteendata elements accessed, one operation may now be performed on sixteendata elements in a parallel fashion. Signed packed byte representation345 illustrates the storage of a signed packed byte. Note that theeighth bit of every byte data element may be the sign indicator.Unsigned packed word representation 346 illustrates how word seventhrough word zero may be stored in a SIMD register. Signed packed wordrepresentation 347 may be similar to the unsigned packed wordin-register representation 346. Note that the sixteenth bit of each worddata element may be the sign indicator. Unsigned packed doublewordrepresentation 348 shows how doubleword data elements are stored. Signedpacked doubleword representation 349 may be similar to unsigned packeddoubleword in-register representation 348. Note that the necessary signbit may be the thirty-second bit of each doubleword data element.

FIG. 3D illustrates an embodiment of an operation encoding (opcode).Furthermore, format 360 may include register/memory operand addressingmodes corresponding with a type of opcode format described in the “IA-32Intel Architecture Software Developer's Manual Volume 2: Instruction SetReference,” which is available from Intel Corporation, Santa Clara,Calif. on the world-wide-web (www) at intel.com/design/litcentr. In oneembodiment, and instruction may be encoded by one or more of fields 361and 362. Up to two operand locations per instruction may be identified,including up to two source operand identifiers 364 and 365. In oneembodiment, destination operand identifier 366 may be the same as sourceoperand identifier 364, whereas in other embodiments they may bedifferent. In another embodiment, destination operand identifier 366 maybe the same as source operand identifier 365, whereas in otherembodiments they may be different. In one embodiment, one of the sourceoperands identified by source operand identifiers 364 and 365 may beoverwritten by the results of the text string comparison operations,whereas in other embodiments identifier 364 corresponds to a sourceregister element and identifier 365 corresponds to a destinationregister element. In one embodiment, operand identifiers 364 and 365 mayidentify 32-bit or 64-bit source and destination operands.

FIG. 3E illustrates another possible operation encoding (opcode) format370, having forty or more bits, in accordance with embodiments of thepresent disclosure. Opcode format 370 corresponds with opcode format 360and comprises an optional prefix byte 378. An instruction according toone embodiment may be encoded by one or more of fields 378, 371, and372. Up to two operand locations per instruction may be identified bysource operand identifiers 374 and 375 and by prefix byte 378. In oneembodiment, prefix byte 378 may be used to identify 32-bit or 64-bitsource and destination operands. In one embodiment, destination operandidentifier 376 may be the same as source operand identifier 374, whereasin other embodiments they may be different. For another embodiment,destination operand identifier 376 may be the same as source operandidentifier 375, whereas in other embodiments they may be different. Inone embodiment, an instruction operates on one or more of the operandsidentified by operand identifiers 374 and 375 and one or more operandsidentified by operand identifiers 374 and 375 may be overwritten by theresults of the instruction, whereas in other embodiments, operandsidentified by identifiers 374 and 375 may be written to another dataelement in another register. Opcode formats 360 and 370 allow registerto register, memory to register, register by memory, register byregister, register by immediate, register to memory addressing specifiedin part by MOD fields 363 and 373 and by optional scale-index-base anddisplacement bytes.

FIG. 3F illustrates yet another possible operation encoding (opcode)format, in accordance with embodiments of the present disclosure. 64-bitsingle instruction multiple data (SIMD) arithmetic operations may beperformed through a coprocessor data processing (CDP) instruction.Operation encoding (opcode) format 380 depicts one such CDP instructionhaving CDP opcode fields 382 an0064 389. The type of CDP instruction,for another embodiment, operations may be encoded by one or more offields 383, 384, 387, and 388. Up to three operand locations perinstruction may be identified, including up to two source operandidentifiers 385 and 390 and one destination operand identifier 386. Oneembodiment of the coprocessor may operate on eight, sixteen, thirty-two,and 64-bit values. In one embodiment, an instruction may be performed oninteger data elements. In some embodiments, an instruction may beexecuted conditionally, using condition field 381. For some embodiments,source data sizes may be encoded by field 383. In some embodiments, Zero(Z), negative (N), carry (C), and overflow (V) detection may be done onSIMD fields. For some instructions, the type of saturation may beencoded by field 384.

FIG. 4A is a block diagram illustrating an in-order pipeline and aregister renaming stage, out-of-order issue/execution pipeline, inaccordance with embodiments of the present disclosure. FIG. 4B is ablock diagram illustrating an in-order architecture core and a registerrenaming logic, out-of-order issue/execution logic to be included in aprocessor, in accordance with embodiments of the present disclosure. Thesolid lined boxes in FIG. 4A illustrate the in-order pipeline, while thedashed lined boxes illustrates the register renaming, out-of-orderissue/execution pipeline. Similarly, the solid lined boxes in FIG. 4Billustrate the in-order architecture logic, while the dashed lined boxesillustrates the register renaming logic and out-of-order issue/executionlogic.

In FIG. 4A, a processor pipeline 400 may include a fetch stage 402, alength decode stage 404, a decode stage 406, an allocation stage 408, arenaming stage 410, a scheduling (also known as a dispatch or issue)stage 412, a register read/memory read stage 414, an execute stage 416,a write-back/memory-write stage 418, an exception handling stage 422,and a commit stage 424.

In FIG. 4B, arrows denote a coupling between two or more units and thedirection of the arrow indicates a direction of data flow between thoseunits. FIG. 4B shows processor core 490 including a front end unit 430coupled to an execution engine unit 450, and both may be coupled to amemory unit 470.

Core 490 may be a reduced instruction set computing (RISC) core, acomplex instruction set computing (CISC) core, a very long instructionword (VLIW) core, or a hybrid or alternative core type. In oneembodiment, core 490 may be a special-purpose core, such as, forexample, a network or communication core, compression engine, graphicscore, or the like.

Front end unit 430 may include a branch prediction unit 432 coupled toan instruction cache unit 434. Instruction cache unit 434 may be coupledto an instruction translation lookaside buffer (TLB) 436. TLB 436 may becoupled to an instruction fetch unit 438, which is coupled to a decodeunit 440. Decode unit 440 may decode instructions, and generate as anoutput one or more micro-operations, micro-code entry points,microinstructions, other instructions, or other control signals, whichmay be decoded from, or which otherwise reflect, or may be derived from,the original instructions. The decoder may be implemented using variousdifferent mechanisms. Examples of suitable mechanisms include, but arenot limited to, look-up tables, hardware implementations, programmablelogic arrays (PLAs), microcode read-only memories (ROMs), etc. In oneembodiment, instruction cache unit 434 may be further coupled to a level2 (L2) cache unit 476 in memory unit 470. Decode unit 440 may be coupledto a rename/allocator unit 452 in execution engine unit 450.

Execution engine unit 450 may include rename/allocator unit 452 coupledto a retirement unit 454 and a set of one or more scheduler units 456.Scheduler units 456 represent any number of different schedulers,including reservations stations, central instruction window, etc.Scheduler units 456 may be coupled to physical register file units 458.Each of physical register file units 458 represents one or more physicalregister files, different ones of which store one or more different datatypes, such as scalar integer, scalar floating point, packed integer,packed floating point, vector integer, vector floating point, etc.,status (e.g., an instruction pointer that is the address of the nextinstruction to be executed), etc. Physical register file units 458 maybe overlapped by retirement unit 154 to illustrate various ways in whichregister renaming and out-of-order execution may be implemented (e.g.,using one or more reorder buffers and one or more retirement registerfiles, using one or more future files, one or more history buffers, andone or more retirement register files; using register maps and a pool ofregisters; etc.). Generally, the architectural registers may be visiblefrom the outside of the processor or from a programmer's perspective.The registers might not be limited to any known particular type ofcircuit. Various different types of registers may be suitable as long asthey store and provide data as described herein. Examples of suitableregisters include, but might not be limited to, dedicated physicalregisters, dynamically allocated physical registers using registerrenaming, combinations of dedicated and dynamically allocated physicalregisters, etc. Retirement unit 454 and physical register file units 458may be coupled to execution clusters 460. Execution clusters 460 mayinclude a set of one or more execution units 162 and a set of one ormore memory access units 464. Execution units 462 may perform variousoperations (e.g., shifts, addition, subtraction, multiplication) and onvarious types of data (e.g., scalar floating point, packed integer,packed floating point, vector integer, vector floating point). Whilesome embodiments may include a number of execution units dedicated tospecific functions or sets of functions, other embodiments may includeonly one execution unit or multiple execution units that all perform allfunctions. Scheduler units 456, physical register file units 458, andexecution clusters 460 are shown as being possibly plural becausecertain embodiments create separate pipelines for certain types ofdata/operations (e.g., a scalar integer pipeline, a scalar floatingpoint/packed integer/packed floating point/vector integer/vectorfloating point pipeline, and/or a memory access pipeline that each havetheir own scheduler unit, physical register file unit, and/or executioncluster—and in the case of a separate memory access pipeline, certainembodiments may be implemented in which only the execution cluster ofthis pipeline has memory access units 464). It should also be understoodthat where separate pipelines are used, one or more of these pipelinesmay be out-of-order issue/execution and the rest in-order.

The set of memory access units 464 may be coupled to memory unit 470,which may include a data TLB unit 472 coupled to a data cache unit 474coupled to a level 2 (L2) cache unit 476. In one exemplary embodiment,memory access units 464 may include a load unit, a store address unit,and a store data unit, each of which may be coupled to data TLB unit 472in memory unit 470. L2 cache unit 476 may be coupled to one or moreother levels of cache and eventually to a main memory.

By way of example, the exemplary register renaming, out-of-orderissue/execution core architecture may implement pipeline 400 asfollows: 1) instruction fetch 438 may perform fetch and length decodingstages 402 and 404; 2) decode unit 440 may perform decode stage 406; 3)rename/allocator unit 452 may perform allocation stage 408 and renamingstage 410; 4) scheduler units 456 may perform schedule stage 412; 5)physical register file units 458 and memory unit 470 may performregister read/memory read stage 414; execution cluster 460 may performexecute stage 416; 6) memory unit 470 and physical register file units458 may perform write-back/memory-write stage 418; 7) various units maybe involved in the performance of exception handling stage 422; and 8)retirement unit 454 and physical register file units 458 may performcommit stage 424.

Core 490 may support one or more instructions sets (e.g., the x86instruction set (with some extensions that have been added with newerversions); the MIPS instruction set of MIPS Technologies of Sunnyvale,Calif.; the ARM instruction set (with optional additional extensionssuch as NEON) of ARM Holdings of Sunnyvale, Calif.).

It should be understood that the core may support multithreading(executing two or more parallel sets of operations or threads) in avariety of manners. Multithreading support may be performed by, forexample, including time sliced multithreading, simultaneousmultithreading (where a single physical core provides a logical core foreach of the threads that physical core is simultaneouslymultithreading), or a combination thereof. Such a combination mayinclude, for example, time sliced fetching and decoding and simultaneousmultithreading thereafter such as in the Intel® Hyperthreadingtechnology.

While register renaming may be described in the context of out-of-orderexecution, it should be understood that register renaming may be used inan in-order architecture. While the illustrated embodiment of theprocessor may also include a separate instruction and data cache units434/474 and a shared L2 cache unit 476, other embodiments may have asingle internal cache for both instructions and data, such as, forexample, a Level 1 (L1) internal cache, or multiple levels of internalcache. In some embodiments, the system may include a combination of aninternal cache and an external cache that may be external to the coreand/or the processor. In other embodiments, all of the cache may beexternal to the core and/or the processor.

FIG. 5A is a block diagram of a processor 500, in accordance withembodiments of the present disclosure. In one embodiment, processor 500may include a multicore processor. Processor 500 may include a systemagent 510 communicatively coupled to one or more cores 502. Furthermore,cores 502 and system agent 510 may be communicatively coupled to one ormore caches 506. Cores 502, system agent 510, and caches 506 may becommunicatively coupled via one or more memory control units 552.Furthermore, cores 502, system agent 510, and caches 506 may becommunicatively coupled to a graphics module 560 via memory controlunits 552.

Processor 500 may include any suitable mechanism for interconnectingcores 502, system agent 510, and caches 506, and graphics module 560. Inone embodiment, processor 500 may include a ring-based interconnect unit508 to interconnect cores 502, system agent 510, and caches 506, andgraphics module 560. In other embodiments, processor 500 may include anynumber of well-known techniques for interconnecting such units.Ring-based interconnect unit 508 may utilize memory control units 552 tofacilitate interconnections.

Processor 500 may include a memory hierarchy comprising one or morelevels of caches within the cores, one or more shared cache units suchas caches 506, or external memory (not shown) coupled to the set ofintegrated memory controller units 552. Caches 506 may include anysuitable cache. In one embodiment, caches 506 may include one or moremid-level caches, such as level 2 (L2), level 3 (L3), level 4 (L4), orother levels of cache, a last level cache (LLC), and/or combinationsthereof

In various embodiments, one or more of cores 502 may performmulti-threading. System agent 510 may include components forcoordinating and operating cores 502. System agent unit 510 may includefor example a power control unit (PCU). The PCU may be or include logicand components needed for regulating the power state of cores 502.System agent 510 may include a display engine 512 for driving one ormore externally connected displays or graphics module 560. System agent510 may include an interface 1214 for communications busses forgraphics. In one embodiment, interface 1214 may be implemented by PCIExpress (PCIe). In a further embodiment, interface 1214 may beimplemented by PCI Express Graphics (PEG). System agent 510 may includea direct media interface (DMI) 516. DMI 516 may provide links betweendifferent bridges on a motherboard or other portion of a computersystem. System agent 510 may include a PCIe bridge 1218 for providingPCIe links to other elements of a computing system. PCIe bridge 1218 maybe implemented using a memory controller 1220 and coherence logic 1222.

Cores 502 may be implemented in any suitable manner. Cores 502 may behomogenous or heterogeneous in terms of architecture and/or instructionset. In one embodiment, some of cores 502 may be in-order while othersmay be out-of-order. In another embodiment, two or more of cores 502 mayexecute the same instruction set, while others may execute only a subsetof that instruction set or a different instruction set.

Processor 500 may include a general-purpose processor, such as a Core™i3, i5, i7, 2 Duo and Quad, Xeon™, Itanium™, XScale™ or StrongARM™processor, which may be available from Intel Corporation, of SantaClara, Calif. Processor 500 may be provided from another company, suchas ARM Holdings, Ltd, MIPS, etc. Processor 500 may be a special-purposeprocessor, such as, for example, a network or communication processor,compression engine, graphics processor, co-processor, embeddedprocessor, or the like. Processor 500 may be implemented on one or morechips. Processor 500 may be a part of and/or may be implemented on oneor more substrates using any of a number of process technologies, suchas, for example, BiCMOS, CMOS, or NMOS.

In one embodiment, a given one of caches 506 may be shared by multipleones of cores 502. In another embodiment, a given one of caches 506 maybe dedicated to one of cores 502. The assignment of caches 506 to cores502 may be handled by a cache controller or other suitable mechanism. Agiven one of caches 506 may be shared by two or more cores 502 byimplementing time-slices of a given cache 506.

Graphics module 560 may implement an integrated graphics processingsubsystem. In one embodiment, graphics module 560 may include a graphicsprocessor. Furthermore, graphics module 560 may include a media engine565. Media engine 565 may provide media encoding and video decoding.

FIG. 5B is a block diagram of an example implementation of a core 502,in accordance with embodiments of the present disclosure. Core 502 mayinclude a front end 570 communicatively coupled to an out-of-orderengine 580. Core 502 may be communicatively coupled to other portions ofprocessor 500 through cache hierarchy 503.

Front end 570 may be implemented in any suitable manner, such as fullyor in part by front end 201 as described above. In one embodiment, frontend 570 may communicate with other portions of processor 500 throughcache hierarchy 503. In a further embodiment, front end 570 may fetchinstructions from portions of processor 500 and prepare the instructionsto be used later in the processor pipeline as they are passed toout-of-order execution engine 580.

Out-of-order execution engine 580 may be implemented in any suitablemanner, such as fully or in part by out-of-order execution engine 203 asdescribed above. Out-of-order execution engine 580 may prepareinstructions received from front end 570 for execution. Out-of-orderexecution engine 580 may include an allocate module 582. In oneembodiment, allocate module 582 may allocate resources of processor 500or other resources, such as registers or buffers, to execute a giveninstruction. Allocate module 582 may make allocations in schedulers,such as a memory scheduler, fast scheduler, or floating point scheduler.Such schedulers may be represented in FIG. 5B by resource schedulers584. Allocate module 582 may be implemented fully or in part by theallocation logic described in conjunction with FIG. 2. Resourceschedulers 584 may determine when an instruction is ready to executebased on the readiness of a given resource's sources and theavailability of execution resources needed to execute an instruction.Resource schedulers 584 may be implemented by, for example, schedulers202, 204, 206 as discussed above. Resource schedulers 584 may schedulethe execution of instructions upon one or more resources. In oneembodiment, such resources may be internal to core 502, and may beillustrated, for example, as resources 586. In another embodiment, suchresources may be external to core 502 and may be accessible by, forexample, cache hierarchy 503. Resources may include, for example,memory, caches, register files, or registers. Resources internal to core502 may be represented by resources 586 in FIG. 5B. As necessary, valueswritten to or read from resources 586 may be coordinated with otherportions of processor 500 through, for example, cache hierarchy 503. Asinstructions are assigned resources, they may be placed into a reorderbuffer 588. Reorder buffer 588 may track instructions as they areexecuted and may selectively reorder their execution based upon anysuitable criteria of processor 500. In one embodiment, reorder buffer588 may identify instructions or a series of instructions that may beexecuted independently. Such instructions or a series of instructionsmay be executed in parallel from other such instructions. Parallelexecution in core 502 may be performed by any suitable number ofseparate execution blocks or virtual processors. In one embodiment,shared resources—such as memory, registers, and caches—may be accessibleto multiple virtual processors within a given core 502. In otherembodiments, shared resources may be accessible to multiple processingentities within processor 500.

Cache hierarchy 503 may be implemented in any suitable manner. Forexample, cache hierarchy 503 may include one or more lower or mid-levelcaches, such as caches 572, 574. In one embodiment, cache hierarchy 503may include an LLC 595 communicatively coupled to caches 572, 574. Inanother embodiment, LLC 595 may be implemented in a module 590accessible to all processing entities of processor 500. In a furtherembodiment, module 590 may be implemented in an uncore module ofprocessors from Intel, Inc. Module 590 may include portions orsubsystems of processor 500 necessary for the execution of core 502 butmight not be implemented within core 502. Besides LLC 595, Module 590may include, for example, hardware interfaces, memory coherencycoordinators, interprocessor interconnects, instruction pipelines, ormemory controllers. Access to RAM 599 available to processor 500 may bemade through module 590 and, more specifically, LLC 595. Furthermore,other instances of core 502 may similarly access module 590.Coordination of the instances of core 502 may be facilitated in partthrough module 590.

FIGS. 6-8 may illustrate exemplary systems suitable for includingprocessor 500, while FIG. 9 may illustrate an exemplary system on a chip(SoC) that may include one or more of cores 502. Other system designsand implementations known in the arts for laptops, desktops, handheldPCs, personal digital assistants, engineering workstations, servers,network devices, network hubs, switches, embedded processors, digitalsignal processors (DSPs), graphics devices, video game devices, set-topboxes, micro controllers, cell phones, portable media players, hand helddevices, and various other electronic devices, may also be suitable. Ingeneral, a huge variety of systems or electronic devices thatincorporate a processor and/or other execution logic as disclosed hereinmay be generally suitable.

FIG. 6 illustrates a block diagram of a system 600, in accordance withembodiments of the present disclosure. System 600 may include one ormore processors 610, 615, which may be coupled to graphics memorycontroller hub (GMCH) 620. The optional nature of additional processors615 is denoted in FIG. 6 with broken lines.

Each processor 610,615 may be some version of processor 500. However, itshould be noted that integrated graphics logic and integrated memorycontrol units might not exist in processors 610,615. FIG. 6 illustratesthat GMCH 620 may be coupled to a memory 640 that may be, for example, adynamic random access memory (DRAM). The DRAM may, for at least oneembodiment, be associated with a non-volatile cache.

GMCH 620 may be a chipset, or a portion of a chipset. GMCH 620 maycommunicate with processors 610, 615 and control interaction betweenprocessors 610, 615 and memory 640. GMCH 620 may also act as anaccelerated bus interface between the processors 610, 615 and otherelements of system 600. In one embodiment, GMCH 620 communicates withprocessors 610, 615 via a multi-drop bus, such as a frontside bus (FSB)695.

Furthermore, GMCH 620 may be coupled to a display 645 (such as a flatpanel display). In one embodiment, GMCH 620 may include an integratedgraphics accelerator. GMCH 620 may be further coupled to an input/output(I/O) controller hub (ICH) 650, which may be used to couple variousperipheral devices to system 600. External graphics device 660 mayinclude be a discrete graphics device coupled to ICH 650 along withanother peripheral device 670.

In other embodiments, additional or different processors may also bepresent in system 600. For example, additional processors 610, 615 mayinclude additional processors that may be the same as processor 610,additional processors that may be heterogeneous or asymmetric toprocessor 610, accelerators (such as, e.g., graphics accelerators ordigital signal processing (DSP) units), field programmable gate arrays,or any other processor. There may be a variety of differences betweenthe physical resources 610, 615 in terms of a spectrum of metrics ofmerit including architectural, micro-architectural, thermal, powerconsumption characteristics, and the like. These differences mayeffectively manifest themselves as asymmetry and heterogeneity amongstprocessors 610, 615. For at least one embodiment, various processors610, 615 may reside in the same die package.

FIG. 7 illustrates a block diagram of a second system 700, in accordancewith embodiments of the present disclosure. As shown in FIG. 7,multiprocessor system 700 may include a point-to-point interconnectsystem, and may include a first processor 770 and a second processor 780coupled via a point-to-point interconnect 750. Each of processors 770and 780 may be some version of processor 500 as one or more ofprocessors 610,615.

While FIG. 7 may illustrate two processors 770, 780, it is to beunderstood that the scope of the present disclosure is not so limited.In other embodiments, one or more additional processors may be presentin a given processor.

Processors 770 and 780 are shown including integrated memory controllerunits 772 and 782, respectively. Processor 770 may also include as partof its bus controller units point-to-point (P-P) interfaces 776 and 778;similarly, second processor 780 may include P-P interfaces 786 and 788.Processors 770, 780 may exchange information via a point-to-point (P-P)interface 750 using P-P interface circuits 778, 788. As shown in FIG. 7,IMCs 772 and 782 may couple the processors to respective memories,namely a memory 732 and a memory 734, which in one embodiment may beportions of main memory locally attached to the respective processors.

Processors 770, 780 may each exchange information with a chipset 790 viaindividual P-P interfaces 752, 754 using point to point interfacecircuits 776, 794, 786, 798. In one embodiment, chipset 790 may alsoexchange information with a high-performance graphics circuit 738 via ahigh-performance graphics interface 739.

A shared cache (not shown) may be included in either processor oroutside of both processors, yet connected with the processors via P-Pinterconnect, such that either or both processors' local cacheinformation may be stored in the shared cache if a processor is placedinto a low power mode.

Chipset 790 may be coupled to a first bus 716 via an interface 796. Inone embodiment, first bus 716 may be a Peripheral Component Interconnect(PCI) bus, or a bus such as a PCI Express bus or another thirdgeneration I/O interconnect bus, although the scope of the presentdisclosure is not so limited.

As shown in FIG. 7, various I/O devices 714 may be coupled to first bus716, along with a bus bridge 718 which couples first bus 716 to a secondbus 720. In one embodiment, second bus 720 may be a low pin count (LPC)bus. Various devices may be coupled to second bus 720 including, forexample, a keyboard and/or mouse 722, communication devices 727 and astorage unit 728 such as a disk drive or other mass storage device whichmay include instructions/code and data 730, in one embodiment. Further,an audio I/O 724 may be coupled to second bus 720. Note that otherarchitectures may be possible. For example, instead of thepoint-to-point architecture of FIG. 7, a system may implement amulti-drop bus or other such architecture.

FIG. 8 illustrates a block diagram of a third system 700 in accordancewith embodiments of the present disclosure. Like elements in FIGS. 7 and8 bear like reference numerals, and certain aspects of FIG. 7 have beenomitted from FIG. 8 in order to avoid obscuring other aspects of FIG. 8.

FIG. 8 illustrates that processors 770, 780 may include integratedmemory and I/O control logic (“CL”) 772 and 782, respectively. For atleast one embodiment, CL 772, 782 may include integrated memorycontroller units such as that described above in connection with FIGS. 5and 7. In addition. CL 772, 782 may also include I/O control logic. FIG.8 illustrates that not only memories 732, 734 may be coupled to CL 872,882, but also that I/O devices 814 may also be coupled to control logic772, 782. Legacy I/O devices 815 may be coupled to chip set 790.

FIG. 9 illustrates a block diagram of a SoC 900, in accordance withembodiments of the present disclosure. Similar elements in FIG. 5 bearlike reference numerals. Also, dashed lined boxes may represent optionalfeatures on more advanced SoCs. An interconnect units 902 may be coupledto: an application processor 910 which may include a set of one or morecores 502A-N and shared cache units 506; a system agent unit 912; a buscontroller units 916; an integrated memory controller units 914; a setor one or more media processors 920 which may include integratedgraphics logic 908, an image processor 924 for providing still and/orvideo camera functionality, an audio processor 926 for providinghardware audio acceleration, and a video processor 928 for providingvideo encode/decode acceleration; an static random access memory (SRAM)unit 930; a direct memory access (DMA) unit 932; and a display unit 940for coupling to one or more external displays.

FIG. 10 illustrates a processor containing a central processing unit(CPU) and a graphics processing unit (GPU), which may perform at leastone instruction, in accordance with embodiments of the presentdisclosure. In one embodiment, an instruction to perform operationsaccording to at least one embodiment could be performed by the CPU. Inanother embodiment, the instruction could be performed by the GPU. Instill another embodiment, the instruction may be performed through acombination of operations performed by the GPU and the CPU. For example,in one embodiment, an instruction in accordance with one embodiment maybe received and decoded for execution on the GPU. However, one or moreoperations within the decoded instruction may be performed by a CPU andthe result returned to the GPU for final retirement of the instruction.Conversely, in some embodiments, the CPU may act as the primaryprocessor and the GPU as the co-processor.

In some embodiments, instructions that benefit from highly parallel,throughput processors may be performed by the GPU, while instructionsthat benefit from the performance of processors that benefit from deeplypipelined architectures may be performed by the CPU. For example,graphics, scientific applications, financial applications and otherparallel workloads may benefit from the performance of the GPU and beexecuted accordingly, whereas more sequential applications, such asoperating system kernel or application code may be better suited for theCPU.

In FIG. 10, processor 1000 includes a CPU 1005, GPU 1010, imageprocessor 1015, video processor 1020, USB controller 1025, UARTcontroller 1030, SPI/SDIO controller 1035, display device 1040, memoryinterface controller 1045, MIPI controller 1050, flash memory controller1055, dual data rate (DDR) controller 1060, security engine 1065, andI²S/I²C controller 1070. Other logic and circuits may be included in theprocessor of FIG. 10, including more CPUs or GPUs and other peripheralinterface controllers.

One or more aspects of at least one embodiment may be implemented byrepresentative data stored on a machine-readable medium which representsvarious logic within the processor, which when read by a machine causesthe machine to fabricate logic to perform the techniques describedherein. Such representations, known as “IP cores” may be stored on atangible, machine-readable medium (“tape”) and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor. For example, IPcores, such as the Cortex™ family of processors developed by ARMHoldings, Ltd. and Loongson IP cores developed the Institute ofComputing Technology (ICT) of the Chinese Academy of Sciences may belicensed or sold to various customers or licensees, such as TexasInstruments, Qualcomm, Apple, or Samsung and implemented in processorsproduced by these customers or licensees.

FIG. 11 illustrates a block diagram illustrating the development of IPcores, in accordance with embodiments of the present disclosure. Storage1130 may include simulation software 1120 and/or hardware or softwaremodel 1110. In one embodiment, the data representing the IP core designmay be provided to storage 1130 via memory 1140 (e.g., hard disk), wiredconnection (e.g., internet) 1150 or wireless connection 1160. The IPcore information generated by the simulation tool and model may then betransmitted to a fabrication facility where it may be fabricated by a3^(rd) party to perform at least one instruction in accordance with atleast one embodiment.

In some embodiments, one or more instructions may correspond to a firsttype or architecture (e.g., x86) and be translated or emulated on aprocessor of a different type or architecture (e.g., ARM). Aninstruction, according to one embodiment, may therefore be performed onany processor or processor type, including ARM, x86, MIPS, a GPU, orother processor type or architecture.

FIG. 12 illustrates how an instruction of a first type may be emulatedby a processor of a different type, in accordance with embodiments ofthe present disclosure. In FIG. 12, program 1205 contains someinstructions that may perform the same or substantially the samefunction as an instruction according to one embodiment. However theinstructions of program 1205 may be of a type and/or format that isdifferent from or incompatible with processor 1215, meaning theinstructions of the type in program 1205 may not be able to executenatively by the processor 1215. However, with the help of emulationlogic, 1210, the instructions of program 1205 may be translated intoinstructions that may be natively be executed by the processor 1215. Inone embodiment, the emulation logic may be embodied in hardware. Inanother embodiment, the emulation logic may be embodied in a tangible,machine-readable medium containing software to translate instructions ofthe type in program 1205 into the type natively executable by processor1215. In other embodiments, emulation logic may be a combination offixed-function or programmable hardware and a program stored on atangible, machine-readable medium. In one embodiment, the processorcontains the emulation logic, whereas in other embodiments, theemulation logic exists outside of the processor and may be provided by athird party. In one embodiment, the processor may load the emulationlogic embodied in a tangible, machine-readable medium containingsoftware by executing microcode or firmware contained in or associatedwith the processor.

FIG. 13 is a block diagram contrasting the use of a software instructionconverter to convert binary instructions in a source instruction set tobinary instructions in a target instruction set according to embodimentsof the invention. In the illustrated embodiment, the instructionconverter is a software instruction converter, although alternativelythe instruction converter may be implemented in software, firmware,hardware, or various combinations thereof. FIG. 13 shows a program in ahigh level language 1302 may be compiled using an x86 compiler 1304 togenerate x86 binary code 1306 that may be natively executed by aprocessor with at least one x86 instruction set core 1316. The processorwith at least one x86 instruction set core 1316 represents any processorthat can perform substantially the same functions as an Intel processorwith at least one x86 instruction set core by compatibly executing orotherwise processing (1) a substantial portion of the instruction set ofthe Intel x86 instruction set core or (2) object code versions ofapplications or other software targeted to run on an Intel processorwith at least one x86 instruction set core, in order to achievesubstantially the same result as an Intel processor with at least onex86 instruction set core. The x86 compiler 1304 represents a compilerthat is operable to generate x86 binary code 1306 (e.g., object code)that can, with or without additional linkage processing, be executed onthe processor with at least one x86 instruction set core 1316.Similarly, FIG. 13 shows the program in the high level language 1302 maybe compiled using an alternative instruction set compiler 1308 togenerate alternative instruction set binary code 1310 that may benatively executed by a processor without at least one x86 instructionset core 1314 (e.g., a processor with cores that execute the MIPSinstruction set of MIPS Technologies of Sunnyvale, Calif. and/or thatexecute the ARM instruction set of ARM Holdings of Sunnyvale, Calif.).

The instruction converter 1312 is used to convert the x86 binary code1306 into alternative instruction set binary code 1311 that may benatively executed by the processor without an x86 instruction set core1314. This converted code may or may not be the same as the alternativeinstruction set binary code 1310 resulting from an alternativeinstruction set compiler 1308; however, the converted code willaccomplish the same general operation and be made up of instructionsfrom the alternative instruction set. Thus, the instruction converter1312 represents software, firmware, hardware, or a combination thereofthat, through emulation, simulation or any other process, allows aprocessor or other electronic device that does not have an x86instruction set processor or core to execute the x86 binary code 1306.

FIG. 14 is a block diagram of an instruction set architecture 1400 of aprocessor, in accordance with embodiments of the present disclosure.Instruction set architecture 1400 may include any suitable number orkind of components.

For example, instruction set architecture 1400 may include processingentities such as one or more cores 1406, 1407 and a graphics processingunit 1415. Cores 1406, 1407 may be communicatively coupled to the restof instruction set architecture 1400 through any suitable mechanism,such as through a bus or cache. In one embodiment, cores 1406, 1407 maybe communicatively coupled through an L2 cache control 1408, which mayinclude a bus interface unit 1409 and an L2 cache 1410. Cores 1406, 1407and graphics processing unit 1415 may be communicatively coupled to eachother and to the remainder of instruction set architecture 1400 throughinterconnect 1410. In one embodiment, graphics processing unit 1415 mayuse a video code 1420 defining the manner in which particular videosignals will be encoded and decoded for output.

Instruction set architecture 1400 may also include any number or kind ofinterfaces, controllers, or other mechanisms for interfacing orcommunicating with other portions of an electronic device or system.Such mechanisms may facilitate interaction with, for example,peripherals, communications devices, other processors, or memory. In theexample of FIG. 14, instruction set architecture 1400 may include aliquid crystal display (LCD) video interface 1425, a subscriberinterface module (SIM) interface 1430, a boot ROM interface 1435, asynchronous dynamic random access memory (SDRAM) controller 1440, aflash controller 1445, and a serial peripheral interface (SPI) masterunit 1450. LCD video interface 1425 may provide output of video signalsfrom, for example, GPU 1415 and through, for example, a mobile industryprocessor interface (MIPI) 1490 or a high-definition multimediainterface (HDMI) 1495 to a display. Such a display may include, forexample, an LCD. SIM interface 1430 may provide access to or from a SIMcard or device. SDRAM controller 1440 may provide access to or frommemory such as an SDRAM chip or module. Flash controller 1445 mayprovide access to or from memory such as flash memory or other instancesof RAM. SPI master unit 1450 may provide access to or fromcommunications modules, such as a Bluetooth module 1470, high-speed 3Gmodem 1475, global positioning system module 1480, or wireless module1485 implementing a communications standard such as 802.11.

FIG. 15 is a more detailed block diagram of an instruction setarchitecture 1500 of a processor, in accordance with embodiments of thepresent disclosure. Instruction architecture 1500 may implement one ormore aspects of instruction set architecture 1400. Furthermore,instruction set architecture 1500 may illustrate modules and mechanismsfor the execution of instructions within a processor.

Instruction architecture 1500 may include a memory system 1540communicatively coupled to one or more execution entities 1565.Furthermore, instruction architecture 1500 may include a caching and businterface unit such as unit 1510 communicatively coupled to executionentities 1565 and memory system 1540. In one embodiment, loading ofinstructions into execution entities 1564 may be performed by one ormore stages of execution. Such stages may include, for example,instruction prefetch stage 1530, dual instruction decode stage 1550,register rename stage 155, issue stage 1560, and writeback stage 1570.

In another embodiment, memory system 1540 may include a retirementpointer 1582. Retirement pointer 1582 may store a value identifying theprogram order (PO) of the last retired instruction. Retirement pointer1582 may be set by, for example, retirement unit 454. If no instructionshave yet been retired, retirement pointer 1582 may include a null value.

Execution entities 1565 may include any suitable number and kind ofmechanisms by which a processor may execute instructions. In the exampleof FIG. 15, execution entities 1565 may include ALU/multiplication units(MUL) 1566, ALUs 1567, and floating point units (FPU) 1568. In oneembodiment, such entities may make use of information contained within agiven address 1569. Execution entities 1565 in combination with stages1530, 1550, 1555, 1560, 1570 may collectively form an execution unit.

Unit 1510 may be implemented in any suitable manner. In one embodiment,unit 1510 may perform cache control. In such an embodiment, unit 1510may thus include a cache 1525. Cache 1525 may be implemented, in afurther embodiment, as an L2 unified cache with any suitable size, suchas zero, 128 k, 256 k, 512 k, 1M, or 2M bytes of memory. In another,further embodiment, cache 1525 may be implemented in error-correctingcode memory. In another embodiment, unit 1510 may perform businterfacing to other portions of a processor or electronic device. Insuch an embodiment, unit 1510 may thus include a bus interface unit 1520for communicating over an interconnect, intraprocessor bus,interprocessor bus, or other communication bus, port, or line. Businterface unit 1520 may provide interfacing in order to perform, forexample, generation of the memory and input/output addresses for thetransfer of data between execution entities 1565 and the portions of asystem external to instruction architecture 1500.

To further facilitate its functions, bus interface unit 1520 may includean interrupt control and distribution unit 1511 for generatinginterrupts and other communications to other portions of a processor orelectronic device. In one embodiment, bus interface unit 1520 mayinclude a snoop control unit 1512 that handles cache access andcoherency for multiple processing cores. In a further embodiment, toprovide such functionality, snoop control unit 1512 may include acache-to-cache transfer unit that handles information exchanges betweendifferent caches. In another, further embodiment, snoop control unit1512 may include one or more snoop filters 1514 that monitors thecoherency of other caches (not shown) so that a cache controller, suchas unit 1510, does not have to perform such monitoring directly. Unit1510 may include any suitable number of timers 1515 for synchronizingthe actions of instruction architecture 1500. Also, unit 1510 mayinclude an AC port 1516.

Memory system 1540 may include any suitable number and kind ofmechanisms for storing information for the processing needs ofinstruction architecture 1500. In one embodiment, memory system 1504 mayinclude a load store unit 1530 for storing information such as bufferswritten to or read back from memory or registers. In another embodiment,memory system 1504 may include a translation lookaside buffer (TLB) 1545that provides look-up of address values between physical and virtualaddresses. In yet another embodiment, bus interface unit 1520 mayinclude a memory management unit (MMU) 1544 for facilitating access tovirtual memory. In still yet another embodiment, memory system 1504 mayinclude a prefetcher 1543 for requesting instructions from memory beforesuch instructions are actually needed to be executed, in order to reducelatency.

The operation of instruction architecture 1500 to execute an instructionmay be performed through different stages. For example, using unit 1510instruction prefetch stage 1530 may access an instruction throughprefetcher 1543. Instructions retrieved may be stored in instructioncache 1532. Prefetch stage 1530 may enable an option 1531 for fast-loopmode, wherein a series of instructions forming a loop that is smallenough to fit within a given cache are executed. In one embodiment, suchan execution may be performed without needing to access additionalinstructions from, for example, instruction cache 1532. Determination ofwhat instructions to prefetch may be made by, for example, branchprediction unit 1535, which may access indications of execution inglobal history 1536, indications of target addresses 1537, or contentsof a return stack 1538 to determine which of branches 1557 of code willbe executed next. Such branches may be possibly prefetched as a result.Branches 1557 may be produced through other stages of operation asdescribed below. Instruction prefetch stage 1530 may provideinstructions as well as any predictions about future instructions todual instruction decode stage.

Dual instruction decode stage 1550 may translate a received instructioninto microcode-based instructions that may be executed. Dual instructiondecode stage 1550 may simultaneously decode two instructions per clockcycle. Furthermore, dual instruction decode stage 1550 may pass itsresults to register rename stage 1555. In addition, dual instructiondecode stage 1550 may determine any resulting branches from its decodingand eventual execution of the microcode. Such results may be input intobranches 1557.

Register rename stage 1555 may translate references to virtual registersor other resources into references to physical registers or resources.Register rename stage 1555 may include indications of such mapping in aregister pool 1556. Register rename stage 1555 may alter theinstructions as received and send the result to issue stage 1560.

Issue stage 1560 may issue or dispatch commands to execution entities1565. Such issuance may be performed in an out-of-order fashion. In oneembodiment, multiple instructions may be held at issue stage 1560 beforebeing executed. Issue stage 1560 may include an instruction queue 1561for holding such multiple commands. Instructions may be issued by issuestage 1560 to a particular processing entity 1565 based upon anyacceptable criteria, such as availability or suitability of resourcesfor execution of a given instruction. In one embodiment, issue stage1560 may reorder the instructions within instruction queue 1561 suchthat the first instructions received might not be the first instructionsexecuted. Based upon the ordering of instruction queue 1561, additionalbranching information may be provided to branches 1557. Issue stage 1560may pass instructions to executing entities 1565 for execution.

Upon execution, writeback stage 1570 may write data into registers,queues, or other structures of instruction set architecture 1500 tocommunicate the completion of a given command. Depending upon the orderof instructions arranged in issue stage 1560, the operation of writebackstage 1570 may enable additional instructions to be executed.

Performance of instruction set architecture 1500 may be monitored ordebugged by trace unit 1575.

FIG. 16 is a block diagram of an execution pipeline 1600 for aninstruction set architecture of a processor, in accordance withembodiments of the present disclosure. Execution pipeline 1600 mayillustrate operation of, for example, instruction architecture 1500 ofFIG. 15.

Execution pipeline 1600 may include any suitable combination of steps oroperations. In 1605, predictions of the branch that is to be executednext may be made. In one embodiment, such predictions may be based uponprevious executions of instructions and the results thereof. In 1610,instructions corresponding to the predicted branch of execution may beloaded into an instruction cache. In 1615, one or more such instructionsin the instruction cache may be fetched for execution. In 1620, theinstructions that have been fetched may be decoded into microcode ormore specific machine language. In one embodiment, multiple instructionsmay be simultaneously decoded. In 1625, references to registers or otherresources within the decoded instructions may be reassigned. Forexample, references to virtual registers may be replaced with referencesto corresponding physical registers. In 1630, the instructions may bedispatched to queues for execution. In 1640, the instructions may beexecuted. Such execution may be performed in any suitable manner. In1650, the instructions may be issued to a suitable execution entity. Themanner in which the instruction is executed may depend upon the specificentity executing the instruction. For example, at 1655, an ALU mayperform arithmetic functions. The ALU may utilize a single clock cyclefor its operation, as well as two shifters. In one embodiment, two ALUsmay be employed, and thus two instructions may be executed at 1655. At1660, a determination of a resulting branch may be made. A programcounter may be used to designate the destination to which the branchwill be made. 1660 may be executed within a single clock cycle. At 1665,floating point arithmetic may be performed by one or more FPUs. Thefloating point operation may require multiple clock cycles to execute,such as two to ten cycles. At 1670, multiplication and divisionoperations may be performed. Such operations may be performed in fourclock cycles. At 1675, loading and storing operations to registers orother portions of pipeline 1600 may be performed. The operations mayinclude loading and storing addresses. Such operations may be performedin four clock cycles. At 1680, write-back operations may be performed asrequired by the resulting operations of 1655-1675.

FIG. 17 is a block diagram of an electronic device 1700 for utilizing aprocessor 1710, in accordance with embodiments of the presentdisclosure. Electronic device 1700 may include, for example, a notebook,an ultrabook, a computer, a tower server, a rack server, a blade server,a laptop, a desktop, a tablet, a mobile device, a phone, an embeddedcomputer, or any other suitable electronic device.

Electronic device 1700 may include processor 1710 communicativelycoupled to any suitable number or kind of components, peripherals,modules, or devices. Such coupling may be accomplished by any suitablekind of bus or interface, such as I²C bus, system management bus(SMBus), low pin count (LPC) bus, SPI, high definition audio (HDA) bus,Serial Advance Technology Attachment (SATA) bus, USB bus (versions 1, 2,3), or Universal Asynchronous Receiver/Transmitter (UART) bus.

Such components may include, for example, a display 1724, a touch screen1725, a touch pad 1730, a near field communications (NFC) unit 1745, asensor hub 1740, a thermal sensor 1746, an express chipset (EC) 1735, atrusted platform module (TPM) 1738, BIOS/firmware/flash memory 1722, adigital signal processor 1760, a drive 1720 such as a solid state disk(SSD) or a hard disk drive (HDD), a wireless local area network (WLAN)unit 1750, a Bluetooth unit 1752, a wireless wide area network (WWAN)unit 1756, a global positioning system (GPS), a camera 1754 such as aUSB 3.0 camera, or a low power double data rate (LPDDR) memory unit 1715implemented in, for example, the LPDDR3 standard. These components mayeach be implemented in any suitable manner.

Furthermore, in various embodiments other components may becommunicatively coupled to processor 1710 through the componentsdiscussed above. For example, an accelerometer 1741, ambient lightsensor (ALS) 1742, compass 1743, and gyroscope 1744 may becommunicatively coupled to sensor hub 1740. A thermal sensor 1739, fan1737, keyboard 1746, and touch pad 1730 may be communicatively coupledto EC 1735. Speaker 1763, headphones 1764, and a microphone 1765 may becommunicatively coupled to an audio unit 1764, which may in turn becommunicatively coupled to DSP 1760. Audio unit 1764 may include, forexample, an audio codec and a class D amplifier. A SIM card 1757 may becommunicatively coupled to WWAN unit 1756. Components such as WLAN unit1750 and Bluetooth unit 1752, as well as WWAN unit 1756 may beimplemented in a next generation form factor (NGFF).

Referring now to FIG. 18, shown is a flow diagram of a method inaccordance with an embodiment of the present invention. Morespecifically, method 1800 shown in FIG. 18 may be performed by compilerlogic to execute on a processor, such as a static or dynamic compilerthat is to generate machine code from incoming source code. Asillustrated, method 1800 begins by identifying at least one variablehaving a compiler directive for in-order handling (block 1810). Asdescribed herein, one or more variables within code can be identified asa particular data type to be handled in order. As such, thisidentification may be based, e.g., on a preamble of a definitionstatement for the variable that identifies to the compiler that thevariable is to be handled in an in-order manner.

Next, control passes to block 1820 where one or more load/storeinstructions in the source code can be identified as being associatedwith one or more of these in-order variables (if any). For example,various load/store instructions within the source code can beidentified. From these identified instructions, the compiler candetermine whether any of these instructions involve a variable to behandled in an in-order manner. In such case, control passes to block1830 where machine code can be generated with in-order load/storeoperations for these identified instructions. In the embodimentsdescribed herein, this machine code may be implemented with specialopcode types that encode such in-order operations. Finally, at block1840 compiled machine code can be emitted from the compiler. Thiscompiled machine code, which in an embodiment may be in an assemblylanguage of an underlying processor architecture (e.g., an x86processor), can be stored in a given storage. For example, this compiledprogram may be stored in a database. From there, the database can beaccessed to obtain the code corresponding to a program, which may thenbe provided, e.g., to a remote source such as a consumer that seeks todownload a given application from the remote database. Of course inother instances, the compiler may execute locally on a system that is tostore and then later execute the machine code. Understand while shown atthis high level in the embodiment of FIG. 18, many variations andalternatives are possible.

Referring now to FIG. 19, shown is a flow diagram of a method inaccordance with another embodiment of the present invention. In theembodiment of FIG. 19, method 1900 may be performed by combinations ofhardware, software, and/or firmware, including hardware circuitry suchas logic within a processor, including front end units such as aninstruction decoder, issue logic and so forth, as well as one or moreexecution units such as one or more load/store execution units withinthe processor. As illustrated, method 1900 begins by receiving anddecoding an ordered load/store instruction in the decoder (block 1910).Thereafter this decoded instruction is provided to a scheduler (block1920). In an embodiment, this scheduler may be implemented in one ormore logics or units of a front end portion of a processor, such asschedule logic, issue logic, order logic and so forth.

Next it is determined whether there is a preceding ordered load/storeinstruction in a scheduling block (diamond 1930). In embodiments, suchscheduling block may encompass a given number of instructions that arescheduled together within an instruction scheduling window or block. Ifit is determined that there is one or more preceding ordered load/storeinstructions, control passes to block 1940 where the decoded orderedload/store instruction may be ordered after such preceding orderedload/store instruction.

Otherwise if at diamond 1930 it is determined that no such precedinginstruction is present within the scheduling block, control passes todiamond 1950 to determine whether there is a succeeding orderedload/store instruction within the scheduling block. If so, controlpasses to block 1960 where the decoded ordered load/store instruction isordered before the succeeding ordered load/store instruction.

Still with reference to FIG. 19, control passes from both of blocks 1940and 1960 and diamond 1950 to block 1970. At block 1970, the decodedordered load/store instruction can be stored in a ready queue with apriority indicator. In an embodiment in which such priority indicator isprovided and used, the indicator may indicate to scheduling logic thatan ordered load/store instruction is to have priority over other,non-ordered instructions.

Still with reference to FIG. 19, next at block 1980 any orderedload/store instructions within the scheduling block may be scheduled inorder. In addition, these instructions (which as discussed above mayhave a priority indicator) may be scheduled with priority, e.g., aheadof non-ordered instructions. Finally, at block 1990 such instructionsmay be executed within a given execution unit (e.g., a given load/storeunit) and retired. Understand while shown at this high level in theembodiment of FIG. 19, many variations and alternatives are possible.

As described above, many variations of instruction generation,identification and execution are possible. Referring now to FIG. 20,shown is a flow diagram of a method for compiler execution in accordancewith an embodiment. As illustrated in FIG. 20, method 2000 may beperformed by a compiler logic to be executed on a processor, such as agiven static or run-time compiler. As seen, method 2000 begins bydetermining whether an instruction received within an instruction stream(e.g., of a source code program being statically or dynamicallycompiled) is a load/store operation (diamond 2010). If not, the givenoperation may be translated to machine code (block 2050). For example, agiven source code operation may be translated into machine code that canbe implemented as one or more assembly instructions.

Still with reference to FIG. 20, if instead at diamond 2010 it isdetermined that a received instruction is a load/store operation,control passes to diamond 2020 to determine whether any operandassociated with the load/store operation is marked with a keyword. In anembodiment, this keyword may be a prefix code or symbol to provide adirective to the compiler that such operand (or address range) is to behandled in order. If such operand/address range is identified within theload/store operation, control passes to block 2040 where an in-orderload/store instruction can be used to represent this load/storeoperation. Control next passes to block 2050, as discussed above.Otherwise, control passes from diamond 2020 to block 2030 where astandard load/store instruction can be used to represent the operation(and thereafter control passes to block 2050). While shown at this highlevel in the embodiment of FIG. 20, many variations and alternatives arepossible.

Referring now to FIG. 21, shown is a flow diagram of a method fordecoding instructions in accordance with an embodiment of the presentinvention. As seen in FIG. 21, method 2100 may be performed at least inpart by hardware circuitry such as decode logic of a front end unit of aprocessor. As illustrated, method 2100 begins by decoding a giveninstruction and marking attributes and dependencies of the instruction(block 2110).

Next it is determined whether the instruction is an in-order instruction(diamond 2120). If not, control passes to block 2130 where this decodedinstruction may be added to a processor data structure, such as astorage within an issue logic of the processor that is coupleddownstream of the decode logic, or other data structure-like list (e.g.,a re-order buffer, depending upon microarchitecture).

Note that if instead it is determined that the decoded instruction is anin-order instruction (as determined at diamond 2120), control passes toblock 2140. At block 2140, the instruction may be added to an in-orderdecoded instruction queue which may be a first-in-first-out (FIFO)queue. Storage in this queue ensures ordering among the controlinstructions. That is, the first instruction in program order will be atthe front of the queue, the second in the second place and so on. Asabove, this queue may be present in issue logic of the processor. Notethat method 2100 may be performed iteratively for incoming instructionsto thus identify and specially handle in-order instructions within aninstruction stream including unordered instructions (and possiblyordered instructions also) and to be executed in an out-of-orderprocessor.

Referring now to FIG. 22, shown is a flow diagram of a method inaccordance with an embodiment of the present invention. Morespecifically, method 2200 may be performed by hardware circuitry such asissue logic of a processor to issue instructions to one or moreexecution units. As seen, method 2200 begins by determining whetherthere is an in-order instruction in-flight (meaning that the instructionis present within the processor, including in a writeback buffer)(diamond 2210). If so, control passes to block 2250 where issue logic ofa processor may perform instruction issuance from the pool ofstandard/out-of-order instructions available in a standard issue datastructure. In standard issuance of instructions, unless two instructionsshare the same processor resource a given instruction is issued toexecution logic for execution. The instructions may execute out-of-orderif the latency of the two instructions are different (e.g., addressingmodes of the instructions are different); or the processor uses a writebuffer between the pipeline and a bus interface unit.

Otherwise, if no in-order instruction is in-flight, control passes todiamond 2220. At diamond 2220, it can be determined whether there is anyin-order instruction available within a ready queue. If not, controlpasses to block 2250, discussed above. If instead there is an availablein-order instruction, control passes to diamond 2230 where it can bedetermined whether the instruction can be issued. This determination maybe based on, e.g., whether prior in-order instructions have beenexecuted. As an example, assume one of the operands needed for thein-order instruction is being computed by a previous out-of-orderinstruction in the execution stage, or a prerequisite out-of-orderinstruction is not yet even placed in the execution stage. In general,at diamond 2230 checks are performed as on an out-of-order instruction.If it is determined at diamond 2230 that the instruction cannot beissued, control passes to block 2250 discussed above. If it isdetermined at diamond 2230 that the instruction can be issued, controlpasses to block 2240 where the instruction is issued to a selectedexecution unit or logic. Understand while shown at this high level inthe embodiment of FIG. 22, many variations and alternatives arepossible.

Referring now to FIG. 23, shown is a block diagram of a portion of aprocessor in accordance with an embodiment. In the embodiment of FIG.23, portions of a pipeline of a processor 2300, which is an out-of-orderprocessor, are shown. As illustrated, a decode unit 2310 is configuredto receive incoming instructions, e.g., macro-instructions received froma fetch unit and decode such instructions into one or moremicro-operations (μops) in a micro-coded case. For a hardware decodingcase, the output of this stage is a sequence of control signals.Depending on the instruction type, decode unit 2310 provides the decodedinstructions to one of multiple locations within an issue unit 2320.

More specifically as seen in FIG. 23, issue unit 2320 includes a firstqueue 2322 for storage of in-order instructions and a second storage2324 for storage of other instructions. In general, these storages areto store decoded instructions and operands/information about operandlocation. First queue 2322 is for storage of the decoded in-orderinstructions, and may be implemented as a FIFO queue. Second storage2324 is for storage of other decoded instructions. As such, in-orderinstructions are issued strictly in the decode order. In anotherembodiment, queue 2322 can be implemented as part of processor datastructure 2324 (which may be a re-order buffer (ROB) in some x86architectures) by adding an indicator to indicate that it is an in-orderinstruction (or not) and another, e.g., 3-4 bit token number,representing the order of arrival from decode unit 2310.

When a given instruction is selected for execution, it is provided fromone of storages 2322 and 2324 to a given one of multiple execution units2330. Depending on the type of instruction, the operation can beprovided to a particular execution unit. Although the scope of thepresent invention is not limited in this regard, execution units 2330may include integer execution units, floating point execution units,vector execution units, load/store execution units, among potentiallyother such execution units. While shown with these limited pipelineportions for ease of illustration, understand that a full pipeline of aprocessor may include additional pipeline units and other logic.

The following examples pertain to further embodiments.

In one example, a processor comprises: a core comprising an out-of-orderpipeline including a decode logic, an issue logic to issue decodedinstructions, and at least one execution logic to execute issuedinstructions of a program, where the at least one execution logic is toexecute at least some instructions of the program out-of-order, thedecode logic to decode a first in-order memory instruction of theprogram and provide the decoded first in-order memory instruction to theissue logic, the issue logic to order the first in-order memoryinstruction ahead of a second in-order memory instruction of theprogram, the first in-order memory instruction an unordered instructionin a source version of the program.

In an example, the first in-order memory instruction is to enable amemory mapped input/output access for the program, where the programcomprises an embedded control application.

In an example, the first in-order memory instruction and the secondin-order memory instruction comprise memory mapped input/outputoperations.

In an example, the issue logic is to issue the first in-order memoryinstruction to the execution logic with a higher priority than thesecond in-order memory instruction.

In an example, a compiler logic is to generate the first in-order memoryinstruction from the unordered memory instruction of the program, basedat least in part on an identifier associated with at least one operandof the unordered memory instruction.

In an example, the compiler logic is to generate the first in-ordermemory instruction having a different machine code than a machine codefor the unordered memory instruction.

In an example, the compiler logic is to generate the first in-ordermemory instruction responsive to a directive indicator of a variabledeclaration, where an operand of the unordered memory instructioncorresponds to a variable of the variable declaration.

In an example, the issue logic comprises: a first storage to storepending in-order memory instructions; and a second storage to storepending unordered instructions.

In an example, the decode logic is to provide the first in-order memoryinstruction to the first storage of the issue logic, the first storagecomprising a first-in-first-out queue.

In an example, the execution logic comprises at least one load/storeexecution unit to execute the first in-order memory instruction.

Note that the above processor can be implemented using various means.

In an example, the processor comprises a SoC incorporated in a userequipment touch-enabled device.

In another example, a system comprises a display and a memory, andincludes the processor of one or more of the above examples.

In another example, a method comprises: identifying a first variablehaving a directive indicator to indicate in-order handling; identifyingan operand of a load/store instruction of a code block associated withthe first variable; translating the load/store instruction to anin-order load/store instruction encoded by a first machine code, toenable execution of the first machine code by an execution logic of aprocessor; and storing the first machine code in a destination storage.

In an example, the method further comprises translating a secondload/store instruction to an unordered load/store instruction encoded bya second machine code, the second load/store instruction not having anoperand associated with a variable marked with a directive indicator.

In an example, the directive indicator comprises a variable directive ina variable declaration for the operand.

In an example, the directive indicator comprises a prefix of thevariable declaration.

In an example, the method further comprises ordering the in-orderload/store instruction ahead of a second in-order load/store instructionassociated with the operand, the second in-order load/store instructionsucceeding the load/store instruction in program order.

In an example, the in-order load/store instruction comprises a write toa device trigger register, and the second in-order load/storeinstruction comprises a read or a write for a device status register.

In an example, the method further comprises ordering one or moreunordered load/store instructions ahead of the in-order load/storeinstruction.

In an example, the operand comprises a memory mapped input/outputlocation.

In an example, the method further comprises ordering a third in-orderload/store instruction of the code block ahead of the in-orderload/store instruction, the third in-order load/store instructionsucceeding the in-order load/store instruction in program order andassociated with a different operand than the operand of the in-orderload/store instruction.

In another example, a computer readable medium including instructions isto perform the method of any of the above examples.

In another example, a computer readable medium including data is to beused by at least one machine to fabricate at least one integratedcircuit to perform the method of any one of the above examples.

In another example, an apparatus comprises means for performing themethod of any one of the above examples.

In another example, a system comprises: a processor including a firstcore having: a decode logic to decode instructions; an issue logic toissue decoded instructions, the issue logic including a first queue tostore in-order memory access instructions and a second storage to storeunordered instructions; and at least one execution logic to executeissued instructions of a program, where the issue logic is to store adecoded first in-order memory access instruction of the program and adecoded second in-order memory access instruction of the program in thefirst queue and store one or more unordered instructions of the programin the second storage, and provide the decoded first in-order memoryaccess instruction to the at least one execution logic ahead of thedecoded second in-order memory access instruction of the program andunordered with respect to one or more of the one or more unorderedinstructions. The system may further include a dynamic random accessmemory coupled to the processor.

In an example, a compiler logic is to generate the first in-order memoryaccess instruction from an unordered memory access instruction, based atleast in part on an identifier associated with at least one operand ofthe unordered memory access instruction, the first in-order memoryaccess instruction having a different machine code than a machine codefor the unordered memory access instruction.

In an example, the at least one operand comprises a memory-mappedinput/output location to be accessed during the program, the programcomprising a device driver for an embedded controller, where the firstcore comprises an out-of-order pipeline.

In another example, an apparatus comprises: means for identifying afirst variable having a directive indicator to indicate in-orderhandling; means for identifying an operand of a load/store instructionof a code block associated with the first variable; means fortranslating the load/store instruction to an in-order load/storeinstruction encoded by a first machine code, to enable execution of thefirst machine code by execution means of the apparatus; and means forstoring the first machine code in a destination storage means.

In an example, the apparatus further comprises means for translating asecond load/store instruction to an unordered load/store instructionencoded by a second machine code, the second load/store instruction nothaving an operand associated with a variable marked with a directiveindicator.

Embodiments may be used in many different types of systems. For example,in one embodiment a communication device can be arranged to perform thevarious methods and techniques described herein. Of course, the scope ofthe present invention is not limited to a communication device, andinstead other embodiments can be directed to other types of apparatusfor processing instructions, or one or more machine readable mediaincluding instructions that in response to being executed on a computingdevice, cause the device to carry out one or more of the methods andtechniques described herein.

Embodiments may be implemented in code and may be stored on anon-transitory storage medium having stored thereon instructions whichcan be used to program a system to perform the instructions. Embodimentsalso may be implemented in data and may be stored on a non-transitorystorage medium, which if used by at least one machine, causes the atleast one machine to fabricate at least one integrated circuit toperform one or more operations. Still further embodiments may beimplemented in a computer readable storage medium including informationthat, when manufactured into a SoC or other processor, is to configurethe SoC or other processor to perform one or more operations. Thestorage medium may include, but is not limited to, any type of diskincluding floppy disks, optical disks, solid state drives (SSDs),compact disk read-only memories (CD-ROMs), compact disk rewritables(CD-RWs), and magneto-optical disks, semiconductor devices such asread-only memories (ROMs), random access memories (RAMs) such as dynamicrandom access memories (DRAMs), static random access memories (SRAMs),erasable programmable read-only memories (EPROMs), flash memories,electrically erasable programmable read-only memories (EEPROMs),magnetic or optical cards, or any other type of media suitable forstoring electronic instructions.

While the present invention has been described with respect to a limitednumber of embodiments, those skilled in the art will appreciate numerousmodifications and variations therefrom. It is intended that the appendedclaims cover all such modifications and variations as fall within thetrue spirit and scope of this present invention.

What is claimed is:
 1. A processor comprising: a core comprising anout-of-order pipeline including a decode logic, an issue logic to issuedecoded instructions, and at least one execution logic to execute issuedinstructions of a program, wherein the at least one execution logic isto execute at least some instructions of the program out-of-order, thedecode logic to decode a first in-order memory instruction of theprogram and provide the decoded first in-order memory instruction to theissue logic, the issue logic to order the first in-order memoryinstruction ahead of a second in-order memory instruction of theprogram, the first in-order memory instruction an unordered memoryinstruction in a source version of the program, wherein a compiler logicis to generate the first in-order memory instruction from an unorderedmemory instruction of the program, based at least in part on anidentifier associated with at least one operand of the unordered memoryinstruction.
 2. The processor of claim 1, wherein the issue logic is toissue the first in-order memory instruction to the at least oneexecution logic with a higher priority than the second in-order memoryinstruction by association of a priority indicator with the firstin-order memory instruction.
 3. The processor of claim 1, wherein thecompiler logic is to generate the first in-order memory instructionhaving a different machine code than a machine code for the unorderedmemory instruction.
 4. The processor of claim 1, wherein the issue logiccomprises: a first storage to store pending in-order memoryinstructions; and a second storage to store pending unorderedinstructions.
 5. The processor of claim 4, wherein the decode logic isto provide the first in-order memory instruction to the first storage ofthe issue logic, the first storage comprising a first-in-first-outqueue.
 6. The processor of claim 5, wherein the issue logic, in responseto a determination that another in-order memory instruction of theprogram is in flight in the processor, is to issue an unorderedinstruction of the program to the at least one execution logic.
 7. Theprocessor of claim 5, wherein the issue logic, in response to a firstdetermination that another in-order memory instruction of the program isnot in flight in the processor and a second determination that one ormore prior in-order memory instructions of the program have beenexecuted, is to issue the first in-order memory instruction to the atleast one execution logic.
 8. The processor of claim 7, wherein theissue logic, in response to a determination that the another in-ordermemory instruction of the program is in flight in the processor, is tonot issue the first in-order memory instruction to the at least oneexecution logic and issue at least one unordered instruction of theprogram to the at least one execution logic.
 9. The processor of claim1, wherein the issue logic, in response to a determination that thefirst in-order memory instruction is in a ready queue but not ready toissue, is to issue at least one unordered instruction of the program tothe at least one execution logic.
 10. The processor of claim 1, whereinthe issue logic is to issue one or more unordered instructions of theprogram to the at least one execution logic unordered with respect tothe first in-order memory instruction.
 11. The processor of claim 1,wherein the first in-order memory instruction comprises a user-levelinstruction of an instruction set architecture to specify in-orderexecution.
 12. A machine-readable medium having stored thereon data,which if used by at least one machine, causes the at least one machineto fabricate at least one integrated circuit to perform a methodcomprising: identifying a first variable having a directive indicator toindicate in-order handling; identifying an operand of a load/storeinstruction of a code block associated with the first variable;translating the load/store instruction to an in-order load/storeinstruction encoded by a first machine code, to enable execution of thefirst machine code by an execution logic of a processor; and storing thefirst machine code in a destination storage.
 13. The machine-readablemedium of claim 12, wherein the method further comprises translating asecond load/store instruction to an unordered load/store instructionencoded by a second machine code, the second load/store instruction nothaving an operand associated with a variable marked with a directiveindicator.
 14. The machine-readable medium of claim 12, wherein themethod further comprises ordering the in-order load/store instructionahead of a second in-order load/store instruction associated with theoperand, the second in-order load/store instruction succeeding theload/store instruction in program order.
 15. The machine-readable mediumof claim 14, wherein the method further comprises ordering one or moreunordered load/store instructions ahead of the in-order load/storeinstruction.
 16. The machine-readable medium of claim 12, wherein themethod further comprises ordering a third in-order load/storeinstruction of the code block ahead of the in-order load/storeinstruction, the third in-order load/store instruction succeeding thein-order load/store instruction in program order and associated with adifferent operand than the operand of the in-order load/storeinstruction.
 17. A system comprising: a processor including a first corehaving: a decode logic to decode instructions; an issue logic to issuedecoded instructions, the issue logic associated with a first queue tostore in-order memory access instructions and a second storage to storeunordered instructions; and a first execution logic to execute issuedinstructions of a program, wherein the issue logic is to store a decodedfirst in-order memory access instruction of the program and a decodedsecond in-order memory access instruction of the program in the firstqueue and store one or more unordered instructions of the program in thesecond storage, wherein a compiler logic is to generate the firstin-order memory access instruction from an unordered memory accessinstruction, based at least in part on an identifier associated with atleast one operand of the unordered memory access instruction; and adynamic random access memory coupled to the processor.
 18. The system ofclaim 17, wherein the issue logic is to provide the decoded firstin-order memory access instruction to the first execution logic ahead ofthe decoded second in-order memory access instruction of the program andunordered with respect to one or more of the one or more unorderedinstructions.
 19. The system of claim 18, wherein the issue logic is toissue the decoded first in-order memory access instruction to the firstexecution logic with a higher priority than the decoded second in-ordermemory access instruction by association of a priority indicator withthe decoded first in-order memory access instruction.
 20. The system ofclaim 17, wherein the at least one operand comprises a memory-mappedinput/output location to be accessed during the program, the programcomprising a device driver for an embedded controller, wherein the firstcore comprises an out-of-order pipeline.